For many Docker seems to be the preferred way of running trytond in production
(Configure Tryton server 5 (good practices or advices))
I don’t know Docker, I’v read a few articles on running Docker in production, it’s not that simple.
So we might start running trytond as a regular service on a vm. And maybe later using Docker.
We would also like to run several trytond services. Each running with it’s own database and log file.
I managed to run 2 services on one vm and it works. (see below)
Is it a good idea to run multiple trytond services like this? We might even run 10, 20 or more.
Or should I learn Docker/Kubernetes/…?
We use Tryton 5.0
● tryton-server.service - Tryton Server WSGI App Loaded: loaded (/lib/systemd/system/tryton-server.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2019-11-07 14:26:44 CET; 1 weeks 1 days ago Docs: man:trytond,file:/usr/share/doc/tryton-server,file:/usr/share/doc/tryton-server-doc,http:doc/tryton.org/ Main PID: 7212 (trytond) Tasks: 1 (limit: 1138) Memory: 24.1M CGroup: /system.slice/tryton-server.service └─7212 /usr/bin/python3 /usr/bin/trytond --config /etc/tryton/trytond.conf --logconf /etc/tryton/trytond_log.conf tdj@debian:~$ systemctl status tryton-server-foo ● tryton-server-foo.service - Tryton Server WSGI App Loaded: loaded (/lib/systemd/system/tryton-server-foo.service; disabled; vendor preset: enabled) Active: active (running) since Sat 2019-11-16 12:11:00 CET; 17min ago Docs: man:trytond,file:/usr/share/doc/tryton-server-foo,file:/usr/share/doc/tryton-server-doc,http:doc/tryton.org/ Main PID: 10037 (trytond) Tasks: 1 (limit: 1138) Memory: 7.3M CGroup: /system.slice/tryton-server-foo.service └─10037 /usr/bin/python3 /usr/bin/trytond --config /etc/tryton/trytond-foo.conf --logconf /etc/tryton/trytond_log-foo.conf