{"repo":"NatoBoram/docker-compose","free":true,"listed":false,"github":"https://github.com/NatoBoram/docker-compose","clone":"git clone https://github.com/NatoBoram/docker-compose.git","description":"My personal homelab","language":"Shell","stars":22,"topics":["docker","docker-compose","homelab"],"license":"AGPL-3.0","category":"deployment-docker-iac","readme_excerpt":"Docker Compose My personal homelab setup using Docker Compose. To get started with your own homelab, take an hour to watch Christian Lempa's videos on Docker: - Docker volumes are at /var/lib/docker/volumes . The daemon.json file goes at /etc/docker/daemon.json . Usage Top-level folders represent a different machine in which Docker Compose is used to manage containers. The machines are: - Corsair (dev machine) - Helion (decommissioned) - Olea (cloud server) - Phantom (current) Each folder contains a compose.yaml that orchestrates the services running on that machine. The compose.yaml file loads services at ${service}/compose.yaml and may expect overrides at compose.override.yaml . You'll have to read service definitions to see what needs to be overridden. Each service has its own .env.${service} file. This is a template that contains all environment variables and their defaults for that service, with empty values serving as documentation. Copy that file to .env.${service}.local and fill in the actual values. The service compose files expect the .env.${service}.local file to exist and won't start without it.","default_branch":null,"files":null,"tree":[],"storefront":"/r/NatoBoram","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/NatoBoram/docker-compose/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}