-
Notifications
You must be signed in to change notification settings - Fork 128
init: systemd info is out of date #383
Comments
Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
Finally, remember to use https://discuss.ipfs.io if you just need general support. |
Hi @RubenKelevra -- thanks for alerting to this. The docs directory in the IPFS website repo is long since deprecated in terms of being used on the site itself, but these really shouldn't be in the repo at all for the sake of being exposed to search. @johnnymatthews -- I know you're on a hot project for a few days, but when you're back in commission, can you please take a look at this directory and make sure there's nothing we need to capture or preserve elsewhere before removing from this repo? Thank you! |
Sure thing! From a quick look it looks like they've been copied directly from |
Well, the issue is, that the troubleshooting section of the readme of the go-ipfs repo points here for help to setup systemd for go-ipfs. So maybe we should just move the outdated sections to misc/*/README.md and update them in the main repository. I feel like they should be placed right next to the service files, since they are more interesting for package maintainer than endusers. Endusers should probably get a best practices sections for servers and desktop installations (apart from the desktop client) in the docs somewhere. |
The init example for systemd is out of date, since we added
Type=notify
support with 0.5.0.There were some additionally improvements to the systemd support. So those changes should be added as well.
Running ipfs as a user (is in my opinion) discouraged, and it should be run as a system service with hardening options instead.
We might want to add informations on how to do both. The hardened and the unhardened service files can be found here:
https://github.com/ipfs/go-ipfs/tree/master/misc/systemd
The text was updated successfully, but these errors were encountered: