This section shows how to deploy ephios in a production environment.
To run ephios (a django project) in production, you generally need:
A python environment (we recommend python3.11).
A WSGI application server (we recommend gunicorn). This will be the program that actually runs the ephios code. Do not use manage.py runserver in production.
A reverse proxy (we recommend nginx) that handles TLS termination, serves static files and proxies requests to the WSGI application server. You should also secure your server using a firewall.
A database (we recommend postgresql) that stores the ephios data.
A program (e.g. cron) that periodically runs a management command (e.g. to send notifications).
A redis instance that is used for caching.
An SMTP server for sending emails.
A domain pointing to your server and a TLS certificate for it.
Generally, ephios can be installed like most django projects. We prepared some guides for common deployment scenarios:
Securing your installation
ephios is a web application and as such it is exposed to the internet. It is therefore important to take some security measures to protect your user data.
You are already using SSL, which is a good start. You should also make sure that your server is up-to-date and that you have a firewall configured to only allow access to the ports you need.
You might want to check out this Mozilla page on how to configure your SSL ciphers and protocols.
The HSTS header is set by ephios to a default of 1 day. After you confirmed your pages and assets are served via SSL correctly, you should increase this value to a year. To do so, add the following environment variables to your ephios environment:
Restart and maybe also add your domain to the HSTS preload list.
You can find the logs of the ephios application inside
Error with None values for date fields when using MySQL
If you are using MySQL, you might encounter errors on date computations like this:
TypeError: "Exception Value: '<' not supported between instances of 'NoneType' and 'NoneType'"
This may be caused by MySQL missing timezone information. You can fix this by running:
# mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -u root -p mysql