The problem is that for morbo and hypnotoad their raison-d'etre is process management in one way or the other. They must be started external to your app so that they can control the reloading of it. If you are trying to release an app, it should never need morbo anyway since that is for development. For deployment, `hypnotoad myapp` works as well as `myapp hypnotoad` would (if that worked), so I don't see much need there. And finally if you really must do a preforking deployment via an app command the 'prefork' command does most of what hypnotoad does, it just can't hot reload.
Cheers, Joel On Monday, March 13, 2017 at 7:40:34 AM UTC-5, Pavel Serikov wrote: > > Hi Sebastian, > > Thanks for a quick feedback. > > Could you please explain more why it's a bad idea to implement hypnotoad > and morbo commands ? > And what is the recommendation in my case, do not release mojolicious apps > as packages, right ? > > понедельник, 13 марта 2017 г., 15:33:21 UTC+3 пользователь sri написал: >> >> Don't do this, if there was a good way to have hypnotoad and morbo >> commands we would already have hypnotoad and morbo commands. >> >> -- >> sebastian >> > -- You received this message because you are subscribed to the Google Groups "Mojolicious" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/d/optout.
