Documentation missing location of config files (and user) #787
Replies: 2 comments
-
It depends. I usually run all web applications written in Python from a single user called The configuration file needs to be readable by the user that als runs Isso. There's no way to drop privileges natively, but certain application servers (I think Gunicorn and uWSGI) can be configured to do so. The name of the configuration file can be anything, there's not default location where Isso would look for a configuration. It is either passed on the command line or using environment variables (described in Deployment). What do you want to change for the documentation? I don't think the documentation should enforce a certain user or even a certain web server. It is a WSGI application and thus is very flexible in its usage (which is hopefully good documented in the deployment document). |
Beta Was this translation helpful? Give feedback.
-
Excuse my noobieness …if I’m running this on Nginx, is just enabling its uwsgi_module enough …or even just depending on the builtin server? I’m confused in that part. |
Beta Was this translation helpful? Give feedback.
-
I’m unable to find in the documentation:
Beta Was this translation helpful? Give feedback.
All reactions