in reply to Developement and production mod_perl sites on a single server

How do you handle setting up concurrent development and production mod_perl sites? ... I've been using two vhosts, two mod_perl startup scripts each instantiating their own TT objects pointing at different template paths and seperate copies of each of my modules. What a nightmare.

Unless you keep your development in a separate sandbox (e.g., a separate instance of Apache listening on a different port), you're asking for mega-trouble. (You're already asking for trouble by using a single box.)

It might simplify things keep one "working" CVS area, and one "production" tree that that can refresh when your production efforts are stable.

  • Comment on Re: Developement and production mod_perl sites on a single server