git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Git Deployment Multiple Existing Environments
@ 2015-09-01  7:50 Sukhwinder Singh
  2015-09-01  8:34 ` Thomas Koch
  0 siblings, 1 reply; 3+ messages in thread
From: Sukhwinder Singh @ 2015-09-01  7:50 UTC (permalink / raw)
  To: git@vger.kernel.org

Hello,
I am kind of new to Git and I have a question regarding using Git for a website. I have searched a lot but haven't found a solution yet. We already have 3-4 environments setup on our Windows servers without Git and each environment already has code which is different from each other.

There are three environments
Live
UAT
Test (has the latest code)


And then developers have their local copies.

We write and test the code locally and manually move each point from one environment to other using merging software and test at each environment.
Now we want to use git because manually moving the code is a lengthy process. Also as the developers have local copies, it is very difficult to manage code.

Code is written locally by the team and then after testing locally it is first merged with "Test" environment code, then "UAT" and then, finally with "Live".
So we have two concerns:

There is different code already existing on these environments.
Testing the code on each environment using the web server.

What is the best way to go about it? As I am new to git more details will be helpful, like commands to use.

Thanks, 		 	   		  

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-09-03  7:30 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-09-01  7:50 Git Deployment Multiple Existing Environments Sukhwinder Singh
2015-09-01  8:34 ` Thomas Koch
     [not found]   ` <BAY180-W19A853193986EA50E27C1BC2680@phx.gbl>
2015-09-03  7:30     ` Thomas Koch

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).