Python web applications
Please first read our documentation about webshares.
- WSGI app directory:
- WSGI entry point:
All new WSGI webshares will come with a dummy app in
Edit this file to load your application.
If you make changes to the source code, you have to tell the webserver to restart the WSGI app by modifying the file time stamp on the WSGI entry point:
Note: SSH access is recommended for developers.
If your app hosts static content, please inform us about the relative path(s)
to the location(s) in
/home/wwwshare/public, that contains static content.
Our WSGI uses a virtual environment (venv), which contains any custom python packages and is activated by our webserver configuration.
If your app needs custom python packages, please specify them in the requirements file. Our deployment will install the venv from the requirements.txt and automatically generate the freeze.txt file, which contains all package versions installed in the venv. The freeze.txt file is needed to reproducibly re-generate the exact state of the venv later, please do not modify this file.
Should there be any changes in the requirements.txt file, we will have to generate a new venv, so please contact us in that case.
Alternatively you can use SSH access to generate the venv yourself. After logging in via SSH, follow the exact steps below:
rm -r private/venv python3 -m venv private/venv private/venv/bin/pip --no-cache-dir install --upgrade pip setuptools wheel private/venv/bin/pip --no-cache-dir install -r private/requirements.txt private/venv/bin/pip --no-cache-dir freeze --local > private/freeze.txt touch public/*.wsgi
But this should not be needed often, since development should happen on your local machine and your app should only be deployed to our server once it is stable.
If your app needs a database connection, please directly include the generated YAML settings from your app:
- Database parameters: