Renovate + Forgejo
from Dust0741@lemmy.world to selfhosted@lemmy.world on 24 Apr 14:52
https://lemmy.world/post/28652030

Are there any guides out there for this? I can’t seem to find anything. Renovates docs are good, but don’t have a lot of detail on setting up the docker image for self hosting.

Thanks!

#selfhosted

threaded - newest

rhymepurple@lemmy.ml on 24 Apr 17:54 next collapse

I think that any guides you find for Gitea + Renovate should work still for Forgejo + Renovate.

I believe the process is:

  • Create Forgejo instance
  • Create a user for Renovate within Forgejo
  • Using the CLI on your local machine (or another tool to complete this step), create an SSH public/private key for the Renovate user
  • Log into Forgejo using the Renovate user and configure the previously created SSH keys and separately generate a Forgejo token
  • Create a Renovate instance with settings for at least RENOVATE_GIT_PRIVATE_KEY (SSH private key value), RENOVATE_TOKEN (Forgejo token value), RENOVATE_PLATFORM (gitea), RENOVATE_ENDPOINT (Forgejo API base URL), and any other Renovate settings that you may find helpful/necessary to configure (eg: GITHUB_COM_TOKEN, RENOVATE_AUTODISCOVER, etc.)
  • Depending on how you want things to work, you may need to give the Renovate Forgejo user access to individual repos
fishynoob@infosec.pub on 25 Apr 01:31 collapse

What does renovate do again?

Dust0741@lemmy.world on 25 Apr 01:56 next collapse

Makes a PR in a repo for updated versions. I.e. you have: image: nginx:1 And it’ll make a PR for the latest version

A CI/CD tool will monitor for changes like this and redeploy.

bob@feddit.uk on 25 Apr 11:42 collapse

Creates endless pain.