Sovereign 8s.is mirror of standardgalactic/collective-homelab-stacks
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
2024-11-30 14:33:59 -05:00
ansible add vm hosts 2024-11-30 14:33:42 -05:00
bookstack fix book stack 2024-10-17 23:24:17 -04:00
dashy remove old comments 2024-10-17 23:24:32 -04:00
grafana fix typo 2024-10-17 23:09:28 -04:00
influxdb fix version tag 2024-10-18 00:10:27 -04:00
k8s modify prometheus 2024-10-18 22:22:07 -04:00
kafka add docs for portainer mount 2023-07-30 09:03:18 -04:00
monica add xoa to docker compose 2023-08-06 00:40:57 -04:00
nginx init 2023-07-09 18:37:22 -04:00
pi-hole roll back to commit 6d1753d 2023-07-23 13:51:18 -04:00
portainer mark trafik as needed to always be running 2024-09-19 23:11:25 -04:00
prometheus rearrange config 2024-11-30 14:33:59 -05:00
uptime-kuma fix typo 2023-07-23 01:27:02 -04:00
xoa change xoa http port 2023-08-06 01:38:10 -04:00
LICENSE Initial commit 2023-07-05 14:02:52 -04:00
README.md Update README.md 2024-09-25 20:51:40 -04:00

collective-homelab-stacks

A collection of homelab docker files, k8s manifest, and anisble playbooks.

Organization

Each grouping of software is in its own folder under the this root folder. Some of these projects, like finance are only one applicaiton. Most of these folders are only just a simple docker compose.

Monitoring

All of the monitoring services (things which I want to talk to promethesus or grafana) get added to monitoring-network.

Portainer

Portainer has this nice feature to define ENVs when you make a stack that are outside of your compose file but can still be used by your services. I am trying to use a gitops still workflow as much as possible, so I want everything to be tracked by git. I don't want to manually put things into portainer. The only thing portainer should do it pull from my github. However, in regards to passwords, many services which are "dockerized" want you to supply a password or other critical information via ENV. If these are tracked with git then I have two options: make the repo private or publish my password to the internet. I don't like either of those.

The problem was the ENV feature in portainer was not documented and I could not get it to work. I finally found the portainer ENV docs.

NOTE: The stack.env file feature from the above docs still does note work. But the individual variables do.

TODO: