: Jessica Garruto [mailto:jgarr...@gmail.com]
Sent: Wednesday, March 10, 2010 8:13 AM
To: cf-talk
Subject: Re: Development and Testing Environment Recommendations
We are fortunate enough to operate in an environment where we are alotted
ample hardware resources, so we can operate separate physical
We are fortunate enough to operate in an environment where we are alotted ample
hardware resources, so we can operate separate physical servers if that's the
recommendation. The point about development failures affecting our test
environment is well-taken. To date, we've not needed to run load
Jess,
Have you considered VM? This could solve the problem without needing another
server.
~|
Want to reach the ColdFusion community with something they want? Let them know
on the House of Fusion mailing lists
Archive:
In an ideal world, do you think we should put both Test and Development
environments on one box (using separate IPs such as
site-dev.siteUrl and site-test.siteUrl), or create multiple sites using
VMware, or utilize two entirely separate servers? And are there
considerations for each of
At work, we handle all of our Dev and QA environments on virtual servers so
we can set it up exactly like production without buying all of the same
hardware twice.
At home, I use VMWare Fusion on my Mac to mimic whatever environment I need
to when developing/testing.
Virtualization gives you
Another vote for VM from me.
elasticserver.com is great-- I have an paid account there, I want to support
them because they are awesome!
Another very nice thing is you can test ANYTHING without worrying about a
sever failing.
Plus, it is very easy to load test an app-- you can limit the memory
6 matches
Mail list logo
