Hello Hello, A friend and I work for a virtual company with several hosted servers in a building far far away and some VPS servers also far far away. Our work is not some great secret, nonetheless I cannot give too many specifics.
Our current setup consists of: A primary (production) web server that hosts our web application. A secondary (test) web server for testing and approval of the web application. Developers have their own private development environments that will vary with each developer as we do not have any requirements except the code actually *work* on the production server! Our work flow is fairly simple. Each developer works in his own environment and on his projects. When a project is complete or in need of feedback that developer will upload his changes/code to the test server. The test server is an exact replica of the production server, obviously. The code is verified to work on the test server as required, and is approved by various quality control people who make sure the code does what they want it to and meets some necessary qualifications due to the industry we are in. When a project is complete, or ready to go, the developer will copy his code from the test server to the production server and then verify they work correctly. As of now, none of the developers have worked on any projects together and have managed to not "step on eachother's toes" so to speak. This is part because we each manage our own projects, but in part because we are a small team and work well together. But! Things are about to change. We are beginning work on a complete re-write and will require much stepping on of toes! We want to incorporate git into our development. I'm not sure if our current setup, as described above, is unique to us or not, but I'm not real clear on how we could best utilize git to help us. I have created a github account and an inital repository containing a clean start of our code. I have documented what I consider to be our workflow moving forward, but nonetheless, I would like some suggestions from anyone using git as well as anyone who might be familiar with a situation such as this. We really don't want to change our setup because of some rigid quality control that must be done, so that really is out of the question. How do we make git work best for our setup? Do we really need to change? Is there a better way for our review process by the QA team? (who are *not* coders at all, btw) Thank you so much for your insight! -- Regards, Nathan England ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ NME Computer Services http://www.nmecs.com Nathan England ([email protected]) Systems Administration / Web Application Development Information Security Consulting (480) 559.9681 /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
