- PHP 77.7%
- Dockerfile 14.8%
- Shell 7.5%
| authentik | ||
| bookstack | ||
| coturn | ||
| dockhand | ||
| dolibarr | ||
| forgejo | ||
| garage | ||
| glpi | ||
| homepage | ||
| immich | ||
| jellyfin | ||
| jmap-webmail | ||
| joplin | ||
| kitchenowl | ||
| miniflux | ||
| nextcloud | ||
| nextgba | ||
| pastebin | ||
| rocketchat | ||
| rustdesk | ||
| searchxng | ||
| stalwart | ||
| traefik | ||
| urbackup | ||
| vaultwarden | ||
| vikunja | ||
| LICENSE | ||
| README.md | ||
Infra_docker
Docker compose files for various services
All of the docker-compose.yml are set to work with traefik.
The variables that need to be changed are beetween <>.
NEWS
- From 26/02/2026 I stopped using the ldap docker. I created the server elsewhere. But, I'm now using Authentik (https://goauthentik.io/). I adapted some of the docker-compose files according to this MAJOR change!
I then use Authentik's dashboard for the application's access. So I stopped using Homepage also. I'll progressively remove labels concerning Homepage.
Authentik and Stalwart through Traefik
In order to use Authentik using traefik, you'll need to add a local entry in your DNS "Authentik public hostname -> Traefik", meaning that you need to set a fix IP address for traefik.
The same principle applies to Stalwart.
Homepage
For the moment I use Homepage (the project is available here: https://github.com/gethomepage) as an applicative dashboard. All the labels "- homepage" are here for that. If you don't want to use it, you can simply remove them. Therefore, if you want to use it, you'll need to create both networks manually:
docker network create --driver=bridge minio
docker network create --driver=bridge web
docker network create --driver=bridge ldap
- 26.02.2026: As written earlier I stopped using Homepage and so I'll remove labels progressively
Networks
The networks declared inside the diferent docker-compose.yml files "web" and "ldap" are here to use the traefik and ldap dockers (that you will find on this git). Again: you can simply remove them if you don't want to use this services.
To do
As you will see, all of the docker-compose files are not using ".env" files at the moment, it's an ongoing process, it will come ;). There are still a lot of work to do, imperfections to correct and new things to add. Don't hesitate to give advises and share your work also!