On 01 May 2013, at 16:41, Nathan England <[email protected]> wrote: > I'm sorry, I didn't make that part clear. We want to use git, and will move > forward > using it individually with our github account as a centralized store for our > code. > > My hesitation begins with how we get our code from our development > environments to the test server. Or the most efficient way to do it... > > 1) can git manage this for us somehow? > 2) should we continue manually copying files from our local dev to the test > server? > > That is what I meant by change. We are not sure how best to manage the > testing. > Maybe a centralized github defeats the purpose and we shouldn't use it? Maybe > there is a better way to get our code to the test server? >
If you are looking for a quick fix you can put git on the test server and just pull updates. Makes life really easy. If you are looking for more automated methods (build processes), they are definitely out there. Many of them. git is a distributed version control system. No need for a centralized location. However, having a machine/server that keeps a copy of all the repositories is handy as a backup and also as a source to pull from. I use UnFuddle (I like the ticket management feature) but there are many places you can use. You are already using github which is quite popular. /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
