skippydippy: I've noticed odd behavior with systemd where if a service crashed it simply won't try to start it when you tell it to. you need to explicitly stop it, then it might try to start again. or maybe there were other ways to fix it, but I never got a really clear understanding of it

I think systemd marks a service as "failed" somehow and then won't try to restart it again unless you explicitly tell it to "stop" the service which will clean up the state. for some reason "restart" doesn't seem to perform the same function

Grinnz: in general I think the idea of automatic restart on crash is a bad one. if something crashes you don't know the state it left things in, so you wouldn't want it to try to start again. however, this issue was about a failed startup during development, so you need to clear the state. you wouldn't want auto restart in that case either

there was an issue where issuing 'reload' wouldn't track the new hypnotoad manager properly because the process exited before it happened, but that was resolved around the time those systemd files were added to the docs

Sadly my push to use Mojo for ongoing production projects at my startup has been quelled. They're going to let the current code stay on Mojo but moving forward everything has to be CodeIgniter because PHP devs are cheaper. =/

CI seems to be an order of magnitude simpler/easier yet just as powerful. Laravel feels more like Mojo, but eh power in CI is in their mentality that filesystem paths are all the routes you'll ever need.