https://github.com/garrett928/collective-homelab-stacks

A collection of homelab docker files, k8s manifest, and ansible playbooks
https://github.com/garrett928/collective-homelab-stacks

Last synced: about 10 hours ago
JSON representation

A collection of homelab docker files, k8s manifest, and ansible playbooks

• Host: GitHub
• URL: https://github.com/garrett928/collective-homelab-stacks
• Owner: garrett928
• License: mit
• Created: 2023-07-05T18:02:52.000Z (over 1 year ago)
• Default Branch: main
• Last Pushed: 2024-10-19T02:33:34.000Z (21 days ago)
• Last Synced: 2024-10-21T12:20:48.094Z (18 days ago)
• Homepage: https://ghart.space
• Size: 561 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# 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](https://www.portainer.io/blog/using-env-files-in-stacks-with-portainer).

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

# TODO: