Hi Nick, why not using nginx and plackup as you describe and use the -R option provided by plackup to watch for example a restart.txt file dedicated for each application.<div>Here is the script I use to start / stop plack for a single app. I think managing more apps with this script should not be a problem</div>
<div><br></div><div>nicolas</div><div><br><div class="gmail_quote">2011/11/11 Nick Knutov <span dir="ltr">&lt;<a href="mailto:mail@knutov.com">mail@knutov.com</a>&gt;</span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hello,<br>
<br>
what is the best way to run (a lot of) Dancer apps in production on shared hosting now?<br>
<br>
I&#39;m the owner and main developer at small hosting company and want to create the environment that allows a lot of users to quick run a lot of Dancer apps.<br>
<br>
I read Dancer::Deployment but didn&#39;t decide anything - Ubic and daemontools don&#39;t looks good way (and Ubic at least requires access to /etc), CGI is slow.<br>
As for now I do manually something like<br>
<br>
plackup -E production -s Starman --workers=4 -l /home/$user/tmp/$app.sock -a bin/<a href="http://app.pl" target="_blank">app.pl</a>  &amp;<br>
<br>
(and I use nginx before app) but it is not easy to start/stop and monitor such apps.<br><font color="#888888">
<br>
-- <br>
Best Regards,<br>
Nick Knutov<br>
<a href="http://knutov.com" target="_blank">http://knutov.com</a><br>
______________________________<u></u>_________________<br>
Dancer-users mailing list<br>
<a href="mailto:Dancer-users@perldancer.org" target="_blank">Dancer-users@perldancer.org</a><br>
<a href="http://www.backup-manager.org/cgi-bin/listinfo/dancer-users" target="_blank">http://www.backup-manager.org/<u></u>cgi-bin/listinfo/dancer-users</a><br>
</font></blockquote></div><br></div>