Document that Syncthing may need extra permissions to access some paths on macOS about docs HOT 5 OPEN

Maybe a link somewhere to whatever Apple documentation exists on allowing applications to access files. I don't know where or what that would be. I don't think it's related to auto-start as such; double-clicking the binary should have the same effect as auto-starting it using launch control.

from docs.

@Joshfindit I guess you're welcome to open a Pull Request and propose text to be added to the documentation. Should come from someone who actually has regular access to a Mac and can verify the procedure. Few of the maintainers qualify in that regard I'm afraid.

I'd agree that neither the Web GUI nor the autostart section would be a good place for this though. Maybe best on https://docs.syncthing.net/intro/getting-started.html or as a FAQ?

from docs.

We don't maintain the brew installer or messages, you should probably inquire in the brew issue tracker.

from docs.

@calmh Thank you, I’ll follow up on that side about the brew messages.

Is there anything that can/should be done in terms of the official documentation?

from docs.

Thank you both for the guidance

double-clicking the binary should have the same effect as auto-starting it using launch control

It unfortunately does not:

• Running it by double-clicking it runs it in the default terminal
• Running it in the terminal (manually or by double-clicking) grants it the permissions of the terminal app (which most likely already has full disk access because it's very annoying to use terminal without it)
• Running it as a service requires that the binary has the required permissions

I think that given this macOS-specific information, it would be helpful to have a note in both https://docs.syncthing.net/intro/getting-started.html (In the 'Installing' subheading, or within a new subheading for example 'Permissions') and https://docs.syncthing.net/users/autostart.html#macos

I'd be happy to submit the PR for either/both.

from docs.