Collection of my docker-compose configs for multiple applications. https://software-berater.net/2020/meine-docker-sammlung/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Christian Aust 0bf9b02a8e Upgrade auf 4.x 4 months ago
daemsing Fix env name error 10 months ago
drone Drone 1.x migration 10 months ago
gitea Gitea server 10 months ago
isso Initial version 10 months ago
matomo Upgrade auf 4.x 4 months ago
nextcloud Version upgrade 5 months ago
software-berater Initial version 10 months ago
.gitignore systemd watcher/path Definition 7 months ago
LICENSE Updated documentation 10 months ago
README.md Gitea ergänzt 10 months ago
dc-watcher@.path systemd watcher/path Definition 7 months ago
dc-watcher@.service systemd watcher/path Definition 7 months ago
dc@.service Extra install entfernt 7 months ago
restart_all.sh Initial version 10 months ago

README.md

Docker file collection

I run a number of applications using Docker and Docker compose. These are the docker-compose files used to orchestrate my services.

In order to use the services, clone this repo into /opt/dockerfiles.

systemd integration

In order to have my apps started at boot time, there's a systemd template config for it. In order to use it, you need to run this command first:

ln -s /opt/dockerfiles/dc@.service /etc/systemd/system/dc@.service

After that you can use standard systemctl commands to control all services by their base directory name:

# enable the service daemsing
systemctl enable dc@daemsing

# disable the service drone
systemctl disable dc@drone

# start the service nextcloud
systemctl start dc@nextcloud

Application secrets

Some apps require base passwords or other secrets set from the environment. Usually this should mean .env files for docker-compose in case I did not forget to provide a template. But I try. :-)