<div dir="ltr">Hi,<div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 16, 2013 at 7:34 PM, Celogeek San <span dir="ltr"><<a href="mailto:me@celogeek.com" target="_blank">me@celogeek.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Use 2 differents plackup start script and listen to a socket. Then use apache or nginx as a proxy</p></blockquote>
<div><br></div><div>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) :)).</div><div><br></div><div>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.</div>
<div><br></div><div>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.</div><div><br></div><div>You can do it with plack::builder though…</div>
<div><br></div><div>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?</div><div><br></div><div>Bye,</div></div>-- <br>Pedro Melo<br>
@pedromelo<br><a href="http://www.simplicidade.org/" target="_blank">http://www.simplicidade.org/</a><br><a href="mailto:xmpp%3Amelo@simplicidade.org" target="_blank">xmpp:melo@simplicidade.org</a><br>mailto:<a href="mailto:melo@simplicidade.org" target="_blank">melo@simplicidade.org</a>
</div></div>