How I Update doco-cd with GitHub / Gitea Actions and Renovate #1090
ronaldheft
started this conversation in
Show and tell
Replies: 2 comments
-
|
Thank you for this guide! 👍 |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Appreciate the writeup. I'm using Renovate + Gitea, and with the recent Doco-CD update with the parallel deployment feature, I am getting some weird behavior, which is probably due to user error on my behalf. My issue: Renovate creates a PR for each image, and Gitea triggers the Doco-CD webhook for each |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
If this is helpful for anyone, I have a simple approach I'm using to version control doco-cd and keep the stack updated with automation. This might be a great alternative to doco-cd managing itself.
renovate.jsonalong with the needed setup for Renovate in my git provider of choice (Gitea).After doing the above, my repo structure roughly looks like this:
renovate.json{ "$schema": "https://docs.renovatebot.com/renovate-schema.json", "extends": [ "config:best-practices" ], "packageRules": [ { "description": "Automerge Docker digest/patch updates after 1 day", "matchManagers": ["docker-compose"], "matchUpdateTypes": ["digest", "patch"], "minimumReleaseAge": "1 day", "automerge": true } ] }update-and-restart.sh:deploy-remote.yml:You will need to checkout the git repo on your server for the first time, but after that, updates can be done through the action anytime the
mainbranch is updated.Beta Was this translation helpful? Give feedback.
All reactions