Corregan recently wrote some quick thoughts about the Atlanta startup scene where he explored some of the benefits of being a part of the community. Also, @jon posted his thoughts on moving his company from San Francisco to St. Louis. Today, I want to explore the largest tech startup scene, the one in Silicon Valley.
Just a quick note that ProjectLocker co-founder Corregan Brown joined the gang at the Atlanta Tech Leaders radio show today. If you’re interested in what goes on behind the scenes at ProjectLocker, give it a listen. Check the archive here:
Atlanta Technology Leaders March 6, 2014
Enjoy!
We often get questions about the easiest way to deploy code from ProjectLocker to a server on the Internet. Perhaps you’re making edits to a staging site, and you want to let your customer always have an up-to-date view of the latest code. Or maybe you want to run frequent load tests against your code on a cloud-based server. Regardless, there’s a lot of interest around automatic deployments. Luckily, ProjectLocker’s Remote Deploy can do this for you!
We’re working on some improvements to Remote Deploy that we think you’ll really like. Part of that will be more documentation and tutorials on how best to use Remote Deploy with your project. This is still in the works, so watch this space for updates.
For now, we do have a preview in the form of a tutorial screencast that shows how to get started with Remote Deployments. Check it out here:
Screencast: How to use Remote Deployment in ProjectLocker.
One of the key reasons teams choose ProjectLocker is that we can help them make the transition to our cloud-based tools from the systems they used before. Whether that means migration assistance, help choosing a Subversion client, or something else, ProjectLocker is here to help.
For years, we’ve also had a handy FAQ for our users who needed answers to commonly-asked questions. Today’ we’re beefing up this FAQ into a full-blown knowledge base. The new knowledge base is powered by Groove and will make it easier to find what you’re looking for. Here are some of the improvements we’ve made with the new knowledge base:
We hope you love it. And as always, please don’t hesitate to let us know what we can do better.
A few months ago, I posted some of the differences between Git and Subversion. In summary: Git and Subversion are different version control systems with different strengths. Neither one is a best fit for every project; you’ll get the best results by examining your team’s needs and choosing the system that is the best fit.
As I mentioned in my prior post, one of the key differences between Subversion and Git is that Subversion knows how to manage fine-grained permissions for your users. So for instance, you can specify that contractors do not have access to code other than their subcomponent, or that new team members have read-only rights on sensitive parts of the repository, or whatever combinations make sense for your workplace.
Subversion has a server-side mechanism that enforces permissions, so that the enforcement is secure and transparent to your users. If you’re managing your own Subversion server, check out the Subversion book section on Path-Based Authorization for details on how to configure feature. If you’re using ProjectLocker, keep reading for an easier way to manage your Subversion Access Control Lists (ACLs).
To get to the Web interface for managing ACLs:
The Subversion Permissions screen gives some background on how to specify
Subscribe via RSS
