Open zerog2k opened 11 months ago
No plans to include that. A user makes things more predictable with respective to paths where things are installed.
Uh, none of the things you list are precluded by a non-login user.
Also, having everything as a subdirectory of $HOME is less predictable then using a purpose-specific directory like /www/octoprint
or similar. What if $HOME
is somewhere weird?
Even if it is somewhere weird, the shell knows where it is. That's the point of $HOME is a variable.
currently, it seems it wants to run only as a user, and only installed from sudo with that user resulting octoprint is running with this non-root user but this requires it to use a real user which has login/shell privilege, and consequently sudo access itself. If possible I'd rather run octoprint with an unprivileged user which cannot login (e.g. shell = /sbin/nologin, etc) and cannot sudo. I wonder if there is a way to run the script as root, but specify either some service user to use, or create, e.g.
octoprint