We have the exact same scenario that Chris talks about in his blog at
the company I work and have found this to be the best way. The great
thing about this is that you can always roll back if things go wrong.
--~--~-~--~~~---~--~~
You received this message because y
Funny! I just got done watching that - I'll post any ?'s on the entry
comment form.
Cheers.
On Apr 17, 9:41 am, "Chris Hartjes" <[EMAIL PROTECTED]> wrote:
> On Thu, Apr 17, 2008 at 10:35 AM, mmayes <[EMAIL PROTECTED]> wrote:
>
> > Any tips/best practices for working with this type of configurat
On Thu, Apr 17, 2008 at 10:35 AM, mmayes <[EMAIL PROTECTED]> wrote:
>
> Any tips/best practices for working with this type of configuration
> would be great, or if there's a better way to do it. For example, when
> rolling out/developing new features, do you use svn, cvs, git, plain
> old ftp,
Hi all,
I was wondering if anybody could provide tips on keeping various
environments in sync?
For example:
I plan on having a local development environment on my computer, say
www.domain.dev
Then I plan on having a testing domain on the live server, like
test.domain.com
Then the production doma
