git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Git: Using Git in a Web Server environment?

From
ABAdam Bourg <adam.bourg@gmail.com>
Date
Jun 30, 2011, 19:18 UTC
Message-ID
<BANLkTimdSvzsRYxE0sDDAoU-84YRb=z9+w@mail.gmail.com>
Background: Reading Pro Git, loving GIt. Git is Awesome!
Servers: 3 Windows Server 2008 w/ 3 SQL Server 2008 servers (3 boxes);
each with a instance of Coldfusion 8.
The servers are:
-Production
-Staging/Testing
-Development
What is the proper way to setup my environment?

I want to be able to elevate code through dev, to testing/staging then to production. I'm thinking the best way is to setup a Git Repository on Production then pull down to Staging then to Dev, then to each of our local machines, then push up in the chains when we need to elevate code to each level.

Is that wise? Are there any hangups or something I should be concerned with? Should I put my production site on Git?

Thank you!
Adam Bourg
Message 1 of 1 in “Git: Using Git in a Web Server environment?”
  1. Adam BourgJun 30, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.