Mount them with Plack? Am 2012-01-26 04:49, schrieb Bill Moseley: A quick questions for the the collective wisdom here.
We have an app that is just getting too big and we are splitting it up into separate Catalyst apps (mostly based on feature) to allow groups of developers to work on features independently, develop tests independently and release independently. Hopefully it will be a more scalable approach. So, /foo and /bar might be on different apps, but all under the same domain in production. But, if using the development servers they would be on different ports. In production we can use the load balancer (or the web server) to direct requests to the right app. But, I need suggestions for development. Currently, the developers start up a proxy server that "points" to their development instances (one or more Catalyst apps). But, that has its own problems (like Apache blocking for some amount of time when a Catalyst dev server is restarted and Apache thinks the server died.) One option I was kicking around was wrapping uri_for to map requests to different paths to different development servers running on different ports. That would simply be per-developer configuration -- meaning each developer has their own "port pool" to use in the case of developers working on the same dev machine. Any other suggestions how to let developers work with related Catalyst apps (that need to link to each other) using the Catalyst development server? Thanks, -- Bill Moseley [email protected]<mailto:[email protected]> _______________________________________________ List: [email protected]<mailto:[email protected]> Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/ *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"* T-Systems Austria GesmbH Rennweg 97-99, 1030 Wien Handelsgericht Wien, FN 79340b *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"* Notice: This e-mail contains information that is confidential and may be privileged. If you are not the intended recipient, please notify the sender and then delete this e-mail immediately. *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*
_______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
