Skip to content

About

My docker compose configuration

Resources

Stars

1 star

Watchers

0 watching

Forks

Latest commit

 

History

31 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Welcome

animation

Intro

Welcome to my github repo, here i save my docker compose setup from across my multiple devices, each containing various services, i hope you find what you need!

Structure

The parent compose file includes the app compose files. app-specific env files are only used where they are actually used. If an app does not have its own .env, it just inherits from the parent .env.

.
├── README.md
├── ayaya.gif
└── <device>
    ├── .env
    ├── .env.example
    ├── docker-compose.yml
    └── <app>
        ├── .env
        ├── .env.example
        └── docker-compose.<app>.yml

Conventions

Container definition

I’m trying to keep the compose files consistent and easy to maintain, so the container definition usually follows this order when the field is actually used:

  • image
  • container_name
  • restart
  • depends_on
  • cpus
  • command
  • user
  • pid
  • tty
  • stdin_open
  • privileged
  • cap_add
  • logging
  • healthcheck
  • labels
  • environment
  • devices
  • volumes
  • ports
  • network_mode
  • networks
  • links

Environment variables

For environment variables, variables live in the parent .env when they’re used across multiple containers, and app-specific values stay in that app’s own .env.

Currently that’s things like TZ, PUID, PGID, DATA_ROOT, MEDIA_ROOT, COMPOSE_ROOT, and DOMAIN.

About

My docker compose configuration

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors