this post was submitted on 13 Apr 2024
8 points (90.0% liked)
DevOps
1661 readers
2 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
What problems are you struggling with specifically?
You basically just pick a system, for example Forgejo - that's comparable to a self-hosted github. Which also comes with github-like actions for CI/CD/Building
If those actions are not good enough for building, you could also self host something like Jenkins or TeamCity
I can deploy these by hand sure, but is that the only way ?
Let's assume forgejo and woodpecker.
I'd need to spin up each service + the db (postgres probably) for each.
Given i'd not have an SCM system or build pipelines until after they were deployed, am i just doing it by hand and hoping for the best or working with something like ansible, saving the scripts to a folder somewhere and manually running them myself?
How about future maintenance or reproducibility?
I'm fully capable of doing it by hand and not against it, just wasn't sure if there was a commonly used bootstrapping mechanism i wasn't aware of.
Ansible files stored locally to bootstrap, then the same set of ansible files gets put in a repo once the repo is up.
IMO