Module::Refresh gave us problems, which is why we advise against using it. If you want reloading, there's always plack's reloading option and Plack::Handler::Shotgun which is the best solution for that: compilation on request. None of those are recommended for production. On Thu, Aug 16, 2012 at 12:33 PM, Alex Knowles <alexk@moonfruit.com> wrote:
On 16/08/12 10:30, Stéphane Wenric wrote:
Perhaps something like supervisor, or nodemon, but adapted to Perl frameworks, could be of use :
http://www.hacksparrow.com/node-js-restart-on-file-change.html http://remysharp.com/2010/10/12/nodejs-rapid-development-nodemon/
They're small utilities which restart your node.js server when they detect that a js file has been modified.
well there's Module::Refresh (which is already built into dancer), but you could put the following in a specific route and it would reload the code afaik:
get '/restart' => sub { Module::Refresh->refresh; };
or something?
a
2012/8/16 David Precious <davidp@preshweb.co.uk>
On Thu, 16 Aug 2012 11:11:13 +0300 sawyer x <xsawyerx@gmail.com> wrote:
An important question would be restarts, IMHO. Since you're doing this properly (PSGI, FastCGI, Starman, etc.), you'll have a service (fcgid, Starman, whatever) running all the time, you'll need to make it possible for the users to restart it.
Indeed.
Depending on the deployment method, it may be possible to add a hook to restart the app automatically on git push or similar perhaps.
Wouldn't work so well for someone SFTP'ing their app up of course :) _______________________________________________ Dancer-users mailing list Dancer-users@perldancer.org http://www.backup-manager.org/cgi-bin/listinfo/dancer-users
_______________________________________________ Dancer-users mailing list Dancer-users@perldancer.org http://www.backup-manager.org/cgi-bin/listinfo/dancer-users