| .forgejo | ||
| audiobookshelf | ||
| firefly | ||
| forgejo | ||
| freshrss | ||
| immich | ||
| invidious | ||
| jellyfin | ||
| komga | ||
| navidrome | ||
| readeck | ||
| vikunja | ||
| .cz.yaml | ||
| .gitignore | ||
| .pre-commit-config.yaml | ||
| .yamllint | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| README.md | ||
| renovate.json | ||
| validate-compose.sh | ||
Chaoslamas compose service
Additional services to https://gitlab.com/jointeg/infrastructure/compose-services. Generally following the same structure and conventions as that repository.
This repository contains docker-compose files for different services, to be deployed on a server. Services will generally be made available via a traefik-reverse proxy (also contained in the repository). In addition we collect metrics for the services via grafana alloy.
Some services have optional modules, generally containing additional configuration (e.g. oidc-configs), which can be added to the service in certain set-ups.
To run a service, you need to provide it with an env-file. Services generally support running multiple instances on one host. For this you need to provide a different COMPOSE_PROJECT_NAME to the service. It is support to name the env-file by the following scheme .env.$COMPOSE_PROJECT_NAME (mind that the COMPOSE_PROJECT_NAME still needs to be provided in the file).
Each service contains a env.sample-file, which you can use as a template for the env-file. Required values, will be uncommented and set to dummyvalue (except if they're to be used as a file-path, in which case they'll be set to .). They need to be replaced for usage.
Every service will contain a settable VERSION-variable (usually prefixed with the service name) to pin the version if required.
In addition it's possible to add docker-compose.override.yaml to a service, to make local adjustments if needed.
Required services
For everything to work, services generally require the traefik-project to be running. There can only be one deployment of traefik for a VM. In addition, the monitoring-project needs to be active. These services must be run from https://gitlab.com/jointeg/infrastructure/compose-services.
Reference the location of that repo in the COMPOSE_SERVICES_CORE_PATH-variable which most services here use for the common images.
Usage
To use a composefile you generally need to add at least a .env-file to the necessary folder. Some services may require additional config-files. You can generally check the env.sample-file for the service to check which variables need to be defined in the .env.