Open babolivier opened 8 years ago
Heard that @nledez will be working on this. Don't let me down, Nicolas.
Hi @babolivier,
An exemple of systemd unit (/etc/systemd/system/cozy.service): `[Unit] Description=Cozy Controller
[Service] Environment=NODE_ENV=production ExecStart=/usr/bin/cozy-controller
[Install] WantedBy=multi-user.target`
BUT if you put systemd without supervisord, the support can be painful (ping @clochix).
And add this to /etc/cozy/controller.json:
"restart_cmd": "/bin/systemctl restart cozy"
Thanks, will look into it for future versions of the package!
@nledez @clochix Any details about this:
BUT if you put systemd without supervisord, the support can be painful (ping @clochix).
?
I just opened an issue in order we document the use of systemd : https://github.com/cozy/cozy-docs/issues/327
Regarding the support, I think the main issue is that it's easier to diagnose problems if everybody use the same configuration. We may don't want to officially support both supervisord and systemd.
Oh, that kind of support. Well, regarding ArchLinux, is not like this is or will ever be an officially supported platform. ;) But we’re able to manage our own issues between us most of time. :p
And as a ArchLinux user, I would definitively go the systemd way. ;)
Another response is:
There are two distribution build with same package:
If we need to support them, we also need to update some scripts.
So. It's more easier for us to manage it.
Another response:
We have more priority on this Debian package before systemd.
@nledez Yes, that’s a different issue with support, but still the same meaning of supported for me: for which you (want to) provide assistance. ;)
My new package at https://aur.archlinux.org/packages/cozy/ use systemd.
The next-coming one (cozy-git, based on V3) will also do.
As most of Archlinux systems run systemd, it'd be better and wiser to use it instead of supervisor. To do this, we need to complete the following steps:
cozy-controller.ini
file (and reload supervisor's configuration)