From: Adam Bourg <adam.bourg@gmail.com>
To: git@vger.kernel.org
Subject: Git: Using Git in a Web Server environment?
Date: Thu, 30 Jun 2011 13:18:40 -0600 [thread overview]
Message-ID: <BANLkTimdSvzsRYxE0sDDAoU-84YRb=z9+w@mail.gmail.com> (raw)
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
reply other threads:[~2011-06-30 19:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTimdSvzsRYxE0sDDAoU-84YRb=z9+w@mail.gmail.com' \
--to=adam.bourg@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).