Struggling with a problem that i just can’t seem to figure out.
When starting from scratch self hosting both the SCM and CI/CD server.
Given that you can’t use an existing setup to deploy/manage it, what is the best practice for deploying said services?
You must log in or register to comment.
my 2 cents here, though I don’t understand all the context, you might take a look at sparky - which is lightweight task runner with web console, so you may throw a bunch of jobs into it to do all the “bootstrapping” so that you may later repeat the same if required on any fresh environment …
I am not sure if it is best practice, but this is what I do and it might provide some inspiration:
- Bootstrap from a private gitlab.com repository with a base ansible setup. Executed from a laptop.
- The bootstrap setups up k8s and installs a bare bones git repository docker container based on https://codeberg.org/al13nsc13nc3/gitsrv.
- Flux CD is installed into the bare bones git repository and k8s.
- Flux CD is used to install Forgejo and Woodpecker CI using the bare bones git repository as the gitops source of truth.
This has the advantage that Gitops and normal git repositories are separate. I think that a similar principle would work with docker compose instead of k8s.