View source for Work-Adventure/install/Add docker-compose as systemd unit

== Docker compose as a systemd unit ==

SystemD calling binaries using an absolute path. In my case is prefixed by <code>/usr/bin</code>, you should use paths specific for your environment.

Create a general <code>/etc/systemd/system/docker-compose@.service</code>:

<pre>
[Unit]
Description=%i service with docker compose
Requires=docker.service
After=docker.service

[Service]
Type=oneshot
RemainAfterExit=true
# for each of your services
# place your .env and docker-compose.yaml files in a subdirectory of the WorkingDirectory
WorkingDirectory=/opt/%i
ExecStart=/usr/bin/docker-compose up -d --remove-orphans
ExecStop=/usr/bin/docker-compose down

[Install]
WantedBy=multi-user.target
</pre>

Place the <code>docker-compose.yaml</code> and <code>.env</code> files of any of your services (traefik-infra, workadventure ...) in a subdirectory of <code>/opt</code> (example <code>/opt/workadventure</code>) and call

<pre>
systemctl start docker-compose@yourservice
</pre>

Example:

For <code>/opt/traefik-infra</code> and <code>/opt/workadventure</code> run
<pre>
systemctl start docker-compose@traefik-infra
systemctl start docker-compose@workadventure
</pre>


To have them started automatically after system boot, run once
<pre>
systemctl enable docker-compose@traefik-infra
systemctl enable docker-compose@workadventure
systemctl daemon-reload
</pre>


== More information and discussion ==

* https://gist.github.com/mosquito/b23e1c1e5723a7fd9e6568e5cf91180f