[Web4lib] web hosting in the cloud

[Francis Kayiwa]

On 2/4/11 10:51 AM, c wrote:
> The situation for me has been that I like the ability to tweak php and mysql
> settings as well as all of my modules on a separate box where I can test the
> results of all those changes without impacting my production environment.
> Truthfully I can get by with a 2 stage environment as long as I completely
> blow away the testing/staging box each time, make it an exact copy of
> production and then run my tests on only one thing at a time.
>
> One thing that has been a difficulty in the past is that I frequently have
> several projects going at the same time. I might be testing something that I
> am working on more long term when an issue comes up on production. If I have
> a 2 stage environment, I then need to wipe the state of staging, recreate it
> from production and work on the highest priority issue, losing some of the
> work I was doing on the longer term project.  That is why I lean towards a 3
> stage environment. Yes, I could have multiple copies of production running
> on the staging server in different directories and just accept that I have
> to be really careful when I am messing about with mysql and php settings.

Have you considered using CVS for this? Let the software do the keeping 
track for you?

./fxk

>


-- 
Past hissy-fits are not a predictor of future hissy-fits --Nick Holland