Docker Organization

[jgwehr]

Describe the solution you'd like

• Easier to stand up or take down services without affecting others (aka, reload Paperless without taking down Dozzle, PiHole)
• A common .env for all services blocks so that ports, secrets can be managed efficiently

Describe alternatives you've considered

• Manage a single .env and copy to directories: https://www.thiscodeworks.com/this-command-puts-a-symlink-of-env-in-every-docker-compose-folder-shellscript/62480e7c8097fe0015b12c44
• Directories for each service "block"

Additional context Add any other context or screenshots about the feature request here.

• [x] Figure out how to do .env (symlinks?)
• [ ] Architect scripts for (1) Install (2) on any upgrade (3) on major upgrades
• [x] Architect Modularity: dependency rules
• [ ] Update Readme: dependency rules
• [x] Rearchitect BACKUP.sh process
• [ ] Update Readme: BACKUP.sh process
• [ ] Update Wiki
• [ ] Update README.md

[jgwehr]

Big breakthrough with symlinks: https://github.com/jgwehr/brewpi/commit/30cef4d29c8966f4e6539006cf5637074ea02f9d

[jgwehr]

Architect Modularity: dependency rules

Each services/ compose stack....

1. Can only have one-way dependency. Stack A can be dependent on Containers within another Stack B, but Stack B cannot also be dependent any Containers in Stack A
2. Can have any time of (efficient) dependencies within itself. Container A can depend on Container B

[jgwehr]

https://docs.docker.com/compose/multiple-compose-files/include/

[jgwehr]

This is nearly done; but need to review documentation. Then finally start doing interesting stuff with this Repo once more!

[jgwehr]

Need to fix some backup formatting: