Forgejo. Gitlab will be overkill probably.
DevOps, simracing, things.
Mastodon: @mariom@ohai.social
Blog: blog.mariom.pl
Forgejo. Gitlab will be overkill probably.
HA can stand for High Availability as well, depends on the context.
If you only use Linux CLI and live in the terminal: pass
There are frontends to pass [1] for different systems, including mobile ones ;) and probably the official list is not complete.
edit: For CLI I prefer gopass [2]
[1] https://www.passwordstore.org/#other
[2] https://github.com/gopasspw/gopass
Probably switching container from gitea to forgejo will just work… I recently switched my deployment, “issues” I had with postgres, but it was related to updates on helm-chart part (gitea upgraded postgres as well, so either update or switch made me same work to do).
For containers (but I use k3s) I use git to store helmfiles and configuration, secrets in ci/cd system.
For the rest - I use autorestic that backups data over ssh and S3.
+1 for renovate.
A little bit different setup - helmfile in git repository + pipelines in woodpecker-ci.
Autorestic, nice wrapper for restic.
Data goes from one server to second server, and vice versa (different provider, different geolocation). And to backblaze B2 - as far as I know cheapest s3-like storage
Funny how many people are joking around those weird activities for some of the meetings like stickers, 2 truths 1 lie, etc etc etc. And we still do it.
According cameras - it’s easier, but in my team we never forced anyone.