Update DOCS.md

[Mariusthvdb]

change to the new (version 11.0.0) homeassistant folder

[frenck]

Converting to draft, as we are currently re-considering this change.

[Mariusthvdb]

ok, sorry, I wasnt aware..
had posted this for some clarification https://community.home-assistant.io/t/samba-add-on-changed-config-to-homeassistant/639230 but if you reconsider that wont be the case..

[frenck]

had posted this for some clarification community.home-assistant.io/t/samba-add-on-changed-config-to-homeassistant/639230 but if you reconsider that wont be the case..

I do not understand that post. This is not designed as a user-facing change. /config is just as normal. The share name simply changed to make a clear difference between the addon configuration (newly added, and being rolled out right now) and Home Assistant configuration.

From all ends, /config will remain to be used.

[boheme61]

Maybe you could just add a symlink in / or /supervisor-folder , and add to smb.gtp1 -file

[share]
follow symlinks = yes

or maybe not, forget it !, i seems to just have realized a symlink in here is to a file(what it seem from samba.org) :)

However the symlink works in cli(login) and over terminal, it's just windows>samba who might need follow-symlink

[langestefan]

I do not understand that post. This is not designed as a user-facing change. /config is just as normal. The share name simply changed to make a clear difference between the addon configuration (newly added, and being rolled out right now) and Home Assistant configuration.

This is a user facing change. This broke the network share of everyone using the samba addon, which must now mount homeassistant instead of config.

[frenck]

Replaced by #3311