Homelab

371 readers

9 users here now

Rules

Be Civil.
Post about your homelab, discussion of your homelab, questions you may have, or general discussion about transition your skill from the homelab to the workplace.
No memes or potato images.
We love detailed homelab builds, especially network diagrams!
Report any posts that you feel should be brought to our attention.
Please no shitposting or blogspam.
No Referral Linking.
Keep piracy discussion off of this community

founded 1 year ago

MODERATORS

communick@selfhosted.forum

rglullis@communick.news

CI/CD Pipeline (alien.top)

submitted 1 year ago by _-Ryick-_@alien.top to c/homelab@selfhosted.forum

4 comments fedilink hide all child comments

With the rapid growth of my self hosted services with a wife and others that use them and my interest in building out my personal experience, I could use some advice on the path of building my own, even if simplistic, CI/CD pipline to keep everything orginized and minimize downtime/broken fetures in production. If anyone has any advice in this area with what to look for and what to avoid, it would be greatly appreciated. Thanks!

you are viewing a single comment's thread
view the rest of the comments

[–] murdaBot@alien.top 1 points 1 year ago (1 children)

To help you with this, you need to tell us what your environment looks like. A CI/CD pipeline for a VM based infrastructure looks VERY different than a fully GitOpsed k8s platform, which looks different than a pipeline for regular Docker containers, which looks different than if you have some cloud infrastructure, etc etc.

[–] _-Ryick-_@alien.top 1 points 1 year ago

It's VM/LXC based (Proxmox). Though, most, if not all, of my front facing services are in a Docker VM. whereas my backend servers are run in LXC containers.