Is it possible for Dancer to have a context-root (java term)? basically: /app1/request /app2/request
This is how things are done in the java web world. Each web archive (containing an entire web application) has a context root binding (based on the file name, or set up explicitly as part of a bigger archive) and the web container (tomcat, jboss, etc.) route the request to the proper app based on that. On Mon, Sep 16, 2013 at 2:54 PM, Pedro Melo <[email protected]> wrote: > Hi, > > On Mon, Sep 16, 2013 at 7:34 PM, Celogeek San <[email protected]> wrote: > >> Use 2 differents plackup start script and listen to a socket. Then use >> apache or nginx as a proxy >> > > That is what he was trying to avoid, and something that is said to be > supported on the docs (at least on the Dancer2::Cookbook) :)). > > Yet, I think the documentation is misleading. What is supported is a > single server with multiple apps, so its a sort of layering: for each > request you test all the routes from all the apps. > > What the poster was looking for was true virtual hosting of multiple > Dancer2 apps in the same process space, and that is still not supported > transparently. > > You can do it with plack::builder though… > > Maybe creating a single App that uses Plack::Builder to split each app > into it's own vhost, and then use Apache2 with that single app? > > Bye, > -- > Pedro Melo > @pedromelo > http://www.simplicidade.org/ > xmpp:[email protected] > mailto:[email protected] > > _______________________________________________ > dancer-users mailing list > [email protected] > http://lists.preshweb.co.uk/mailman/listinfo/dancer-users > >
_______________________________________________ dancer-users mailing list [email protected] http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
