DevOps

1670 readers

7 users here now

DevOps integrates and automates the work of software development (Dev) and IT operations (Ops) as a means for improving and shortening the systems development life cycle.

Rules:

Posts must be relevant to DevOps
No NSFW content
No hate speech, bigotry, etc
Try to keep discussions on topic
No spam of tools/companies/advertisements
It’s OK to post your own stuff part of the time, but the primary use of the community should not be promotional content.

Icon base by Lorc under CC BY 3.0 with modifications to add a gradient

founded 1 year ago

MODERATORS

Ategon@programming.dev

RandomDevOpsDude@programming.dev

Self Hosted SCM & CI/CD Chicken and Egg (programming.dev)

submitted 7 months ago by Senal@programming.dev to c/devops@programming.dev

11 comments fedilink hide all child comments

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 are viewing a single comment's thread
view the rest of the comments

[–] icb4dc0de@programming.dev 2 points 5 months ago (1 children)

I tend to do manual bootstrapping with local execution as well but when using Forgejo/Gitea and corresponding actions you could also init the repo, start building your pipeline and use act to run it (locally at first if course) and as soon as you have your infrastructure in place you could continue to use the same pipeline there?

Still not ideal/perfect but if you don’t want to depend on some SaaS then this at least already runs the automation as it will be later?

[–] Senal@programming.dev 1 points 5 months ago (1 children)

Yeah, I'm going with a tiny dedicated infra bootstrapping box with all the tools I'd need to bootstrap the main infrastructure.

Using a hypervisor (proxmox in this case) I have some prebuilt vms's and container images that I can use for the bootstrap instances so i'd not need to completely hand roll it again should it be needed.

I'm looking at cloudinit scripts to see if that's useful for this.

I really like packer but I'm hesitant to rely on anything hashicorp until whatever they have going on shakes out.

Then I just load up the bootstrap box with the main infra code and use woodpecker to deploy.

Code and config backed up, also mirrored to newly created infra forgejo instances, just in case.

If I can get a semi presentable cloud init based bootstrap system working nicely I'll stick it somewhere people can get to it, in case it's useful to someone else.

[–] icb4dc0de@programming.dev 1 points 5 months ago

If you don’t mind I’d be interested in how the cloudinit for proxmox looks like 😁 So far I only used it for Azure and Hetzner Cloud to bootstrap Coder machines but from your description I’d expect that should work. Very cool approach!