Selfhosted

I'm gonna be real: You want kubernetes + gitops (either fluxcd or argocd or the rancher one).

I mean sure, jenkins works, but nothing is going to be as smooth as kubernetes. I originally attempted to use ansible as many people suggested, but I got frustrated becuase it struggled to manage state in a truly declarative way (e.g. when I would change the ports in the ansible files the podman containers wouldn't update, I had to add tasks for destroying and recreating the containers).

I eventually just switched to kubernetes + fluxcd. I push to the git repo. The state of the kubernetes cluster changes according. Beautiful. Simple. Encrypted secrets via sops. It supports the helm package manager as well. Complex af to set up though. But it's a huge time saver in the long run, which is why so many companies use it.

as @damnthefilibuster@lemmy.world already mentioned: GitLab CI

Jenkins is a CI application from before CI was cool. GitLab CI is integrated and can trigger on certain events. Additionally you mentioned, that you want to publish on a public repo anyway.

You are probably are comfortable with containers. So GitLab CI should be easy for you to learn - as it pretty much starts up a container to do certain tasks. I've seen suggestions for Kubernetes, which for sure is the more mature solution. But i would question, whether you need the added functionality and complexity of K8s for a home setup.

To gain access to your local network, you can use the runner for a secure connection (as described by damnthefilibuster). or you could SSH into the machine, as long as you have it in a DMZ. Drawback is that you have to be more sure about your network infrastructure. Benefit is that it is a more general approach. Obviously you need to store all certs, keys and preferably even addresses in secrets, not the .gitlab-ci.yml.

As you can see from this thread, there are many ways which lead to rome. My advice is to start with something simple and lightweight, which you understand. adding complexity down the road is easier, than removing it.

I've heard Ansible is not ideal for docker compose.

Not sure what you heard, but I use ansible to push docker compose files to VMs and publish containers without issue. Works nicely.

I usually create systemd service files to start/stop the compose jobs and have ansible set it all up.

I did Jenkins for a while. It works, but it was built before the world of containers and is now fairly antiquated. Most extensions are no longer maintained.

Look into forgejo, and then use actions to auto deploy

Isn't Jenkins a continuous integration system? I'd think that you'd want a configuration management system (like ansible) if you're not trying to set up CI infrastructure.

I've used Ansible to deploy docker compose and it worked pretty well. You will have to do some learning if you aren't familiar with it, but I'd say it's worth it.

Like others, I would not recommend Jenkins.

I use Ansible to deploy a bunch of containers with intradependencies (shared volumes, networks and settings). One of the containers is homemade with the source pulled from codeberg. Variables are kept in a separate file and passwords in an encrypted one and the whole thing is in a private repo. It is quite flexible.

When I started out converting from compose, I literally asked Copilot for "this, but in Ansible", which got me pretty far.

You wanna know a fun way to do this?

GitHub (and I think Gitlab too) supports you running their runner within your own infra. It’s literally a binary that needs permissions and space. Then, you can tell your git repo to use that runner to run docker compose and as part of the “build” process, deploy you container to the same or an in-network machine.

This is not secure, it’s probably going to involve a lot of hard coding of local IPs or server names etc. But you can make it work.

I use this way to get a Win11 PC to run some regular containers on itself. Works like a charm.

Why? Tools for this exist. Jenkins is not that tool.