Akoya has asked for the wisdom of the Perl Monks concerning the following question:

Esteemed monks,

I am designing a Catalyst application (my first), which I hope to run as a single instance, with single sign-on, across multiple subdomains.

I have found the Catalyst::Action::SubDomain module, which looks very promising. The documentation is fairly sparse, and does not addresses any domain/server configuration required in order to run a single instance as I propose.

My questions are:

  1. In order to have a single Catalyst app instance running across multiple subdomains, must those subdomains be mirrored domains (i.e., using Apache's ServerAlias directive)?
  2. In order to have single sign-on between domains, must I use a wildcard domain in the session cookie?
  3. Most of all, is Catalyst::Action::Subdomain the best choice for determining within my app which domain the request is going to, so that the app can be customized for each domain?

Thank you for your time and consideration.

There are 10 types of people in this world...those who grok binary, and those who don't.
  • Comment on Running a single instance of a Catalyst app across multiple subdomains with single sign-on

Replies are listed 'Best First'.
Re: Running a single instance of a Catalyst app across multiple subdomains with single sign-on
by stonecolddevin (Parson) on Dec 23, 2009 at 19:56 UTC

    I should think that you should be able to point each virtual host to the same instance and have it Just Work. An external FastCGI process would handle this nicely, or a standalone HTTP::Prefork process.

    As far as the SSO stuff, you should be able to do something like a wildcard as you suggested so that the base domain has access to all the subdomain cookies.

    mtfnpy

[reply]

      Thanks, dhoss, I'll give it a try.

      There are 10 types of people in this world...those who grok binary, and those who don't.
[reply]

Back to Seekers of Perl Wisdom