You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i just realized, that its not only systemd (#135) which needs a script for automated startup. basically, its the same thing with sys-v like systems. we should also provide an init.d script.
how do you start cherrymusic on the testserver so far? using screen? how do you autostart at boot? (you are not using rc.local, are you?) running cherrymusic with root is bad practice.
The text was updated successfully, but these errors were encountered:
Well, actually, since the test-server doesn't ever shut down, we just use screen. The only times when cherrymusic has to be stopped, is when we get the newest features via git. so essentially, I didn't ever have the need for it to start up automatically. But you are right. Any server should be startable using sysv or system-d as a daemon... Gotta look into that.
I have just uploaded cherrymusicd, which can demonize cherrymusic. We can simply symlink cherrymusicd into /etc/rc.d or wherever the distro specific init scripts are hiding. So this would have to be done for each distibution. As this is not part of cherrymusic, but of the packaging, I will close this issue now. @6arms1leg, maybe you could set up a repo for the PKGBUILD of cherrymusic on arch, so we can take care of that together.
i just realized, that its not only systemd (#135) which needs a script for automated startup. basically, its the same thing with sys-v like systems. we should also provide an init.d script.
how do you start cherrymusic on the testserver so far? using screen? how do you autostart at boot? (you are not using rc.local, are you?) running cherrymusic with root is bad practice.
The text was updated successfully, but these errors were encountered: