diff --git a/docs/installation-production.md b/docs/installation-production.md index 9fd396775381aee42d3fbe89c20116b537a450d5..86a5651e2af15c3bd23aa745baed121cc75cc0ab 100644 --- a/docs/installation-production.md +++ b/docs/installation-production.md @@ -8,6 +8,8 @@ - [Configuration](#configuration) - [Running Engine](#running-engine) - [Running with Systemd](#running-with-systemd) + - [Combined Unit for Engine Core and Liquidsoap](#combined-unit-for-engine-core-and-liquidsoap) + - [Individual Units for Engine Core and Liquidsoap](#individual-units-for-engine-core-and-liquidsoap) - [Running with Supervisor](#running-with-supervisor) - [Logging](#logging) - [Read more](#read-more) @@ -223,12 +225,13 @@ For this you can utilize either [Systemd](https://systemd.io/) or [Supervisor](h ### Running with Systemd + +#### Combined Unit for Engine Core and Liquidsoap + Copy the unit file `/opt/aura/engine/config/systemd/aura-engine.service` to `/etc/systemd/system/`. This unit file starts engine-core and engine-liquidsoap within one command. Here Liquidsoap is started as -as subprocess. - -> Please note not to use any other unit files in that directory yet. They are work in progress. +as subprocess. For more fine-grained control the units in the next section are recommended instead. Now you'll need to reload the Systemd unit files @@ -260,6 +263,38 @@ sudo systemctl restart aura-engine sudo systemctl status aura-engine ``` +#### Individual Units for Engine Core and Liquidsoap + +Copy the unit files `/opt/aura/engine/config/systemd/aura-engine-lqs.service` and +`/opt/aura/engine/config/systemd/aura-engine-core.service` to `/etc/systemd/system/`. + +Now you'll need to reload the Systemd unit files + +```shell +sudo systemctl daemon-reload +``` + +**Start Liquidsoap and check its status** + +```shell +sudo systemctl start aura-engine-lqs +sudo systemctl status aura-engine-lqs +``` + +**Start Engine Core and check its status** + +```shell +sudo systemctl start aura-engine-core +sudo systemctl status aura-engine-core +``` + +**Use journalctl to observe the logs** + +```shell +sudo journalctl -f +``` + + ### Running with Supervisor Now, given you are in the engine's home directory `/opt/aura/engine/`, simply type following to start