in reply to How to build multirealm Catalyst application

A single app would be fine. Just mod_rewrite the urls (since you're using apache) to the appropriate app urls. and use $c->uri_for_action over the nasty string passing to uri_for. Things just get messy if you do that. Plus, it gives you the benefit of only needing to know the private path, with Catalyst taking care of generating the URL properly, in case you decide to move things around or change names/API.

mtfnpy

Replies are listed 'Best First'.
Re^2: How to build multirealm Catalyst application
by roman (Monk) on Jul 26, 2010 at 06:02 UTC

    Thanks for your reply. One app seems more and more maintainable for me. But there is one thing I can't get

    I can imagine that mod_rewrite turns http://provider.mycatapp.xyz/order/123 into http://mycatapp.xyz/provider/order/123

    But which piece of code converts the http://mycatapp.xyz/provider/payments (result of $c->uri_for_action('/provider/payments')) back into http://provider.mycatapp.xyz/payments?

[reply]

      I don't have hardly any mod_perl experience, however, I'm fairly certain they way you would do this in nginx is to mess with the say, fastcgi params (if you were in fact deploying to fastcgi). Basically Catalyst just needs to know the base url a given domain consists of. I will look around to see if I can find anything more coherent regarding this.

      mtfnpy

[reply]

In Section Seekers of Perl Wisdom