fcfcdbeb234ea39ce0ca058c6e58327580f0ab52
Prosody changed its role scheme to only support a single primary role for each user. In addition, the names of the built-in roles have been changed. We thus follow those changes to be compatible with the most recent trunk. One open question is whether we should switch admin -> operator here, too (operator being a server-wide admin), but so far there's no need to.
Snikket Web Portal
Development quickstart
$ direnv allow
$ cp example.env .env
$ $EDITOR .env # to adapt the configuration to your needs
$ pip install -r requirements.txt
$ pip install -r build-requirements.txt
$ make
$ quart run
Configuring
Purely via environment variables
For a list of required and understood environment variables as well as their
semantics, please refer to example.env.
Via python code
In addition to statically setting environment variables, it is possible to
initialise the environment variables in a python file. To do that, pass the
path to the python file as SNIKKET_WEB_PYENV environment variable.
The python file is evaluated before further environment variable processing takes place. Every name defined in that file which begins with an upper case ASCII letter is included in the processing of environment variables for configuration purposes.
For a (non-productive) example of such a file, see example.env.py.
Languages
Python
46.1%
HTML
34.7%
SCSS
13.3%
Jinja
2.9%
Shell
1%
Other
2%
