https://github.com/sottey/sottey-docker-compose
Docker compose files I have worked on
https://github.com/sottey/sottey-docker-compose
docker docker-compose homelab self-hosted selfhosted
Last synced: 3 months ago
JSON representation
Docker compose files I have worked on
- Host: GitHub
- URL: https://github.com/sottey/sottey-docker-compose
- Owner: sottey
- License: mit
- Created: 2024-10-30T02:48:26.000Z (8 months ago)
- Default Branch: main
- Last Pushed: 2024-10-30T03:10:54.000Z (8 months ago)
- Last Synced: 2025-04-10T18:33:02.343Z (3 months ago)
- Topics: docker, docker-compose, homelab, self-hosted, selfhosted
- Homepage:
- Size: 38.1 KB
- Stars: 2
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# docker-compose
Docker compose files I have toyed with and used
Each folder contains a docker compose file that I altered to run cleanly on my system. Many of these I simply pasted into [Dockge](https://github.com/louislam/dockge). Some were more complex and were run using the docker CLI.
I like to have a directory in my home dir named "docker-data" which is where I put a seperate directory for each instance. Inside that the container creates the needed folders.
for simplicity, each compose file uses it's own DB (if needed). I have been debating whether this is the way to go or if I should just have a container for each of postgres, mariadb, mysql, etc. For now, it is explicit DB's in the compose file.
As time goes on, I will add a README to each folder with thoughts and tips specific to the respective application