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.
|
1 month ago | |
---|---|---|
daemsing | 7 months ago | |
drone | 7 months ago | |
gitea | 7 months ago | |
isso | 7 months ago | |
matomo | 1 month ago | |
nextcloud | 2 months ago | |
software-berater | 7 months ago | |
.gitignore | 4 months ago | |
LICENSE | 7 months ago | |
README.md | 7 months ago | |
dc-watcher@.path | 4 months ago | |
dc-watcher@.service | 4 months ago | |
dc@.service | 4 months ago | |
restart_all.sh | 7 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.
daemsing
a CMS website based on Ruby and the comfortable mexican sofa CMS systemdrone
my CI/CD installation of drone.iogitea
my installation of Gitea - Git with a cup of teaisso
a comment system to go with my static website, based on issomatomo
the Matomo statistics softwarenextcloud
my Nextcloud instance on Dockersoftware-berater
my static website software-berater.net
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. :-)