Skip to content

Consider scheduling default maintenance crons @midnight instead of @every 24h #16107

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jpraet opened this issue Jun 8, 2021 · 0 comments · Fixed by #16431
Closed

Consider scheduling default maintenance crons @midnight instead of @every 24h #16107

jpraet opened this issue Jun 8, 2021 · 0 comments · Fixed by #16431
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.
Milestone

Comments

@jpraet
Copy link
Member

jpraet commented Jun 8, 2021

The basic maintenance crons are scheduled @every 24h by default:
https://docs.gitea.io/en-us/config-cheat-sheet/#basic-cron-tasks---enabled-by-default

In practice, this means they will be triggered every 24h from the time that gitea has started.

I realize these default schedules can be overridden in app.ini (which I have done on my instance), but doesn't it make sense to schedule these at a fixed time with typically less user impact like @midnight?

@lunny lunny added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Jun 8, 2021
@lafriks lafriks added this to the 1.16.0 milestone Jul 14, 2021
@go-gitea go-gitea locked and limited conversation to collaborators Oct 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants