-
Notifications
You must be signed in to change notification settings - Fork 584
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New profile: syncthing #6536
New profile: syncthing #6536
Conversation
Btw, I think this is "good enough" but this is the type of service which would be better implemented as a systemd unit file. |
previously #295 |
mkdir ${HOME}/.local/state/syncthing | ||
whitelist ${HOME}/.local/state/syncthing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this program intended to be executed at the user or system level?
Does the syncthing
executable act as the client, server or both?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Answer is both for both questions.
Ideally it is a user service. Most commonly it is system service. But upstream likes everyone to just run the program in a terminal and then minimize it.
Then it is a peer in a network which will connect to all sorts of things (announce servers, relay servers, other peers), while also exposing servers for LAN auto-discovery and to receive other peer's connections. And on top of all that the local web server with the HTML interface.
Let's go with it, thanks @gcb. I will remove the program from src/firecfg/firecfg.config for now, also removed some of the noise (see above kmk3's discussions). |
https://docs.syncthing.net/
tested with v1.28.0