mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2024-11-10 04:05:42 +01:00
abf72a42e7
The https://v$major.next.forgejo.org instances are polling for new releases with a cron job every hour. This is not only a waste of resources because there is nothing most of the time, it also imposes a delay of maximum one hour when there is a new release. When the release is published, notify the corresponding instance that an upgrade is ready. In the request will 404 but leave a trace in the logs which can trigger an upgrade script if wakeup-on-logs is configured accordingly. GET https://v$major.next.forgejo.org/.well-known/wakeup-on-logs/forgejo-v$major * v8 - a daemon watching on the web server logs was installed for https://v8.next.forgejo.org and will perform the upgrade. * v7 - nothing will happen for https://v7.next.forgejo.org because it still relies on the hourly cron job. * v1.21 - nothing will happen because https://v1.next.forgejo.org does not exist. See also: * https://forgejo.org/docs/next/developer/infrastructure * https://code.forgejo.org/infrastructure/wakeup-on-logs |
||
---|---|---|
.. | ||
backport.yml | ||
build-release-integration.yml | ||
build-release.yml | ||
cascade-setup-end-to-end.yml | ||
e2e.yml | ||
mirror.yml | ||
publish-release.yml | ||
renovate.yml | ||
testing.yml |