Skip to content
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

Should set API key in environment #92

Open
calmh opened this issue Jan 20, 2019 · 2 comments
Open

Should set API key in environment #92

calmh opened this issue Jan 20, 2019 · 2 comments

Comments

@calmh
Copy link
Member

calmh commented Jan 20, 2019

I don't remember if we've already talked about this somewhere / sometime, but it would be neat if syncthing-macos automatically set an API key in the environment. As is, if the API key is wrong things will stay "offline" unnecessarily.

(Is it a supported mode of operation to have a syncthing backend started outside of syncthing-macos? If not, we don't really need to have this configurable at all.)

@xor-gate
Copy link
Member

xor-gate commented Jan 20, 2019

We could dispatch running syncthing daemon with launchd automatically configured from the application. Not sure how easy it would be from Swift.

@xor-gate
Copy link
Member

xor-gate commented Aug 9, 2020

In my opinion the macOS bundle/application should only work with its own syncthing instance and the API key discovery on first run is already in implemented by you reading out the XML file with a delay time. I'm not sure what you mean by "set an API key in the environment" as it is only used in the scope of the REST client.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants