However the Pi it runs on is not: if the entire Pi somehow crashed or was unplugged, then when it rebooted someone would have to manually start the server and open the browser again. These things should automatically happen on startup.
This issue is only #probablyfix because the above is annoying but quick to do with the mouse and keyboard already attached to the server Pi, whereas restarting the panels would require SSH'ing via another system. Also, automatically starting Chrome, once the server has started, is slightly more complex than just running the panel script.
The server is run under a process monitor already: https://github.com/wearhere/spacecontrol/blob/b8356f7/gulpfile.js#L149
However the Pi it runs on is not: if the entire Pi somehow crashed or was unplugged, then when it rebooted someone would have to manually start the server and open the browser again. These things should automatically happen on startup.
This issue is only #probablyfix because the above is annoying but quick to do with the mouse and keyboard already attached to the server Pi, whereas restarting the panels would require SSH'ing via another system. Also, automatically starting Chrome, once the server has started, is slightly more complex than just running the panel script.