Recent searches
Search options
Two new blog posts are up!
Come take a look at how I have configured Renovate to run on my self-hosted Forgejo runners. Now you can easily track the applications that need to be updated on your Docker Compose, and probably anything else that you might be running on your home lab (as long as they are tracked in Git). 1/2
https://mteixeira.wordpress.com/2025/02/16/running-renovate-on-self-hosted-forgejo/
@badnetmask@hachyderm.io so how does it actually deploy the docker-compose changes after the renovate MR is merged?
@badnetmask@hachyderm.io@rachel
Right now I don't have any automation to deploy the changes. That's pending an issue where I am unable to run my Ansible Execution Environment from a workflow. So, for now, Renovate proposes the change, I merge, then run Ansible to deploy manually.
One thing I don't like though, but I haven't put some time to check: one of the containers had a new version released before I shipped the previous one, so I ended up with two pull requests (it didn't close the first). Need to figure out what happened here.
@badnetmask@hachyderm.io it should update the MR
Can be an issue with apps that need strict upgrade paths
@badnetmask@hachyderm.io oh it can create two MRs if there is a major update and you have the full version tagged
@rachel
Yeah, I'm not gonna stress about it right now. I closed the old and merged the new. I'll deal with that if it happens again.