Open tynes opened 5 years ago
I was looking into this earlier today. Should we assume that the workflow is the user installing hsd globally via npm? Seems like service files expect a path (although we can technically use which hsd, I believe).
I think that a systemd service file, as well as any other service manager files, is best located within OS package manager code, e.g. a Homebrew formula or pacman package. This removes the need to assume how a user is installing hsd. Perhaps, we could include example files and make it clear that a user cannot use the example as-is, i.e. they will need to specify installation paths, etc.
If anyone needs one of these let me know. I've built one for our internal HSD infrastructure.
It would be nice to have a base
systemd
service filehsd.service
included in theetc
directory along with instructions on how to use it. This would allow users to starthsd
as a service and allow for features such as automatic restart.