As you transition, you'll also probably need to do some work in your development environment. In our experience, each developer needs their own dev server because as you're working and changing things, you need to restart the server often. You also want to work on a personal server with just one child so you don't drive yourself crazy when different code gets loaded into different children.

This happens because when you're using Apache::Registry, your code is loaded into memory when an apache child responds to a request. As you're developing, you change things often, and if you forget to restart your server, the old code can still be in memory. I find this can happen especially for people used to a CGI environment.

For us, setting up an environment to have personal server required some work. We finally landed on a system that uses a shared apache binary, but allows developers to have their own config file, logs, etc.