Tighten Docker access in the self-host script
The self-hosting deploy script now uses only the Docker access it needs, so the other accounts on a shared server keep exactly the permissions they had before the install.
- Changed how the script reaches Docker for users outside the docker group: it now runs its Docker commands through sudo and no longer changes the permissions of the Docker socket. If an earlier install left the socket open to every account, the script warns and shows the one-line command that restores the default.
- Removed Docker access from the reverse proxy, which now reads its routes from a generated file, and made the configuration files readable by their owner only from the moment they are created.
- Updated the requirements: install Docker before running the script, and run it from a directory only you can write to. Keys no longer appear in the process list while it runs.
