-
-
Notifications
You must be signed in to change notification settings - Fork 91
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
[syncthing] Mount only /media
, /share
and /backups
#458
Comments
We should reconsider this since people actually like to sync HA-internal files, it appears. So maybe even do the opposite of the above and expose |
I would suggest that we enable the mount but add a warning in the addon Readme about the security risk. |
I would just like to second the idea of allowing exposure to /config perhaps with a warning, as I personally have been using Syncthing to edit files in /config via other devices. |
That sounds reasonable. I think that people could generally use some guidance with the different persistent directories available to Syncthing. Maybe we should just include a table similar to this one with a short explanation of each dir? Unfortunately, the official documentation about these dirs (documented under the |
@salim-b The table is a nice idea. That would be a great thing to have. |
How to sync /config folder? I have several redundant servers that need to have up-to-date information with automatic synchronization of configuration files |
Being able to sync |
I agree with @alucryd. I had mentioned this issue before. The |
Thank you @salim-b for helping to fix this issue! |
I was wondering whether we should limit the mounts (
map
inconfig.yaml
) byssl
read-only, i.e. remove the:rw
, or even completely removingssl
. Why does Syncthing need access to custom certs in the first place? We have Ingress for that, no?addons:rw
. What is the use case for Syncthing having access to local add-ons? Not even the official File editor add-on has access toaddons
since it's deemed confusing for non-developers.The text was updated successfully, but these errors were encountered: