Just in case someone is curious about the outcome of the production level installation with the apache2/gunicorn combination.
In a nutshell: the system is up and running, the tryton server can be accessed through the internet (I tested that with a desktop client, not with the web client).
What I did:
Prerequisite: webserver linked to a domain name with a DNS A record and port 8000 open.
- follow edbo’s post by the book Deploying Tryton with a Python virtual environment
to the point where the gunicorn server is started and a systemd file is created. At this point the trytond server can be started with user@host:/$ systemctl start trytond - follow gunicorn behind Apache web server – ServerOK to configure apache
in the virtual host file adjust ServerName, ServerAdmin, DocumentRoot, ErrorLog, CustomLog, ProxyPass and ProxyPassReverse to the settings of your system.
ProxyPass / http://(your domain ip):8000/
ProxyPassReverse / “http://(your domain ip):8000/” - enable your virtual host configuration (a2ensite (virtualhost).conf)
- restart the apache2 server
If the gunicorn server is running you can reach your trytond server through the internet at http://<your.domain>