Link: https://github.com/renovatebot/renovate

I'm quite happy with my #forgejo replacement for #github. i was missing dependabot enforced correctness and installed a Renovate container. IMO it's an improvement over the github approach. love it.

#SelfHosting #DigitalSovereignty #Homelab #OwnYourData

https://github.com/renovatebot/renovate

I have been running renovate on my yaml files, been really happy with it. Even got notifications set up finally so it tells me what gets upgraded to what.
Although for me it is not a constant container but a Cron job that runs in my k3s cluster (since I'm using k3s anyway)

I use renovate bot for my self-hosted forgejo. It works pretty well but I think the documentation could be better. I had some settings in my config.js that was supposed to go into my repo's renovate.json and I had no idea

oh? something specific you can share?

i've not setup notifications. my forgejo does that for me, which i'm running podman style. since i live in a van, i host my stuff on hetzner and i'm trying to see how much i can do on one of their smaller instances ;-) so, i'm not running in constantly. a systemd timer runs it over night. otherwise it was very much doing a lot of heavy re-scanning.

So I haven't tested this specific example (but it should work):

"packageRules": [
    {
      "matchDatasources": ["docker"],
      "matchPackageNames": ["ghcr.io/netbootxyz/netbootxyz"],
      "versioning": "regex:^(?<major>\\d+)\\.(?<minor>\\d+)\\.(?<patch>\\d+)-nbxyz(?<build>\\d+)$"
    }
  ]

Netboot.xyz has its docker images tagged in a non-standard way necessitating a custom package rule so that renovate bot can properly pick up updates. I thought this went into the config.js that renovate bot uses for its own configuration but no it goes in your repo's renovate.json file like so:

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": [
    "config:recommended"
  ],
  "packageRules": [
    {
      "matchDatasources": ["docker"],
      "matchPackageNames": ["ghcr.io/netbootxyz/netbootxyz"],
      "versioning": "regex:^(?<major>\\d+)\\.(?<minor>\\d+)\\.(?<patch>\\d+)-nbxyz(?<build>\\d+)$"
    }
  ],
  "assignees": [
    "UntouchedWagons"
  ],
  "reviewers": [
    "UntouchedWagons"
  ]
}

I've been running a relatively simple setup with forgejo and renovate tracking docker-compose/podman yaml files which has largely been unproblematic. Although I have been really struggling to configure renovate to properly find updates for forgejo's own containers that are hosted on codeberg. If anyone is having renovate pull in image updates for forgejo on codeberg I'd really appreciate any pointers

@UntouchedWagons @opennomad yes I do that makes my repos updated in GitHub. I uses ‪kubeara.dev‬ for the renovate config/deployment and make my stufff easy to control everything from one dashboard to.

We use renovate for dep updates (for lemmy-ui), and a self-hosted woodpecker CI for lemmy.

CI is imo the more dangerous way people are linking their projects to github.

i used to be ok with the trade-offs, but it's no longer feeling safe. i even paid for the plan for a long time, but i'm not looking back. forgejo and renovate are more performant and featureful. total win :-)

I actually saw this being used before I knew GitHub had one. Seemed reliable to me!