[Catalyst] Development environments and performance

[John Goulah]

On Jan 16, 2008 12:51 PM, <Wade.Stuart at fallon.com> wrote:

> "John Goulah" <jgoulah at gmail.com> wrote on 01/16/2008 11:13:06 AM:
>
> >
> >
> >
> > Why wouldn't you just use the standalone server bundled with
> > Catalyst?  Fcgi is great for production, but the processes are
> > fairly thick memory wise, so having instances for each developer
> > could be an issue.   We use the cat server for development and works
> > fine for about 5-10 people at any given time on a modest box (4G ram)
>
> Could be a massive assumption,  but usually when you go through the cost
> (time, cap) of building out a dev server environment you want it to mirror
> your production servers as much as possible so that you spend time
> squishing bugs that may exist in your production environment -- not some
> other different environment.  If they are using FCGI in prod it makes
> perfect sense to do so in dev.  Why battle bugs that may be introduced on
> the standalone server, or worse miss bugs that _do_ affect your production
> environment because you are developing on a different environment?
>
>

No, you want your staging environment to mirror prod as closely as
possible.  You shouldn't be pushing straight from dev to prod, if you are
you should rethink your process.   We are running a production app and the
dev servers work great - very rarely do we see a bug in the production
environment that cant be replicated in dev, however, thats why we have a
stage to catch the edge cases and overall QA and -that- runs in the exact
environment as prod.

Also, one box per dev is a fine solution, if you ensure everyone is using
the same modules.  But I've seen it happen where some developer is using a
different module version than prod and that can cause much greater issues.
Either way I'd recommend maintaining a Makefile.PL + local::lib to resolve
this.  If you build the prod modules from the same Makefile this problem
typically goes away.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.scsys.co.uk/pipermail/catalyst/attachments/20080116/ec486=
d5b/attachment.htm