You may reuse it of course, just run a setup as root (or copy your config to the root home folder, or provide a path to the config file in the gateway run command with --config-dir option).
Just gateway run uses parameters from config.yaml and seems ignore your --access option…
It collect the usage statistics (not personalized), you may disable it with option tracing.enabled: false in your config.yaml (root one, if you run it as root), or with an argument --tracing.enabled=false in your gateway run command.
no. More like a warning - usually you should not run anything as root, it’s not safe.
It’s better to use a special limited user for that, especially when the service is not require any root access (like in this case).
This is not possible, if you did it correctly and this user has an access to this file, remember - it’s looking for ~/.local/share/storj/gateway/config.yaml
So, if the user is USER, the path would be /home/USER/.local/share/storj/gateway/config.yaml
However, if you use sudo, it will looking for config for the root, i.e. /root/.local/share/storj/gateway/config.yaml