Hi Racke, On Friday 26.09.2014 16:20:46 Stefan Hornburg (Racke) wrote:
On 09/26/2014 04:06 PM, Lutz Gehlen wrote: [...]
So far, so good, but then - after variable amounts of time as sketched
above, this:
Dancer 1.3123 server 13413 listening on http://0.0.0.0:3000
The problem is that obviously, from now on the server is not reachable under port 7000 any more, and eventually, my testers complain and I have to restart the server.
As you can see, the process ID does not change. Does the server exec itself forgetting the command line parameters? Or what else happens? I hope someone can help me avoid this behaviour.
My recommendation is not to use the builtin web server at all.
You could use same deployment for live and development, just with a different Dancer environment.
Which is usually quite simple with plackup and an init script.
Thanks for your quick reply. I'm testing plackup with Starman now. Cheers, Lutz