-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Add gitea manager reload-templates command #24843
Conversation
This can be useful to update custom templates in production mode, when they are updated frequently and a full gitea restart each time is disruptive.
This might be a bit obscure, I'm not sure how generally useful this functionality is. But our templates display things like release status and ongoing projects, and it's nice to be able to update those without risking e.g. data loss when submitting comments or failed git repository access to update those. |
Maybe we also need a template load test sub command to do a test before real reload. |
I see the original PR doesn't have so, and I do not think there is a real case which really requires "testing". If there is any error, the old templates are still used. Do you think this is a must? If no, I would suggest to keep things simple (no test). @lunny |
If the reload failure will not break the old templates I agree we don't need the test. |
This reverts commit 3849b33.
I removed the |
* upstream/main: Fix install page context, make the install page tests really test (go-gitea#24858) Add validations.required check to dropdown field (go-gitea#24849) Use Go 1.20 for next release (go-gitea#24859) Add gitea manager reload-templates command (go-gitea#24843) Remove `In your repositories` link in milestones dashboard (go-gitea#24853) Fix 500 error when select `No assignee` filter in issue list page (go-gitea#24854) Add IsErrRepoFilesAlreadyExist check when fork repo (go-gitea#24678) Fix missing yes/no in delete time log modal (go-gitea#24851) Fix document and improve comment (go-gitea#24844) # Conflicts: # web_src/css/base.css
This can be useful to update custom templates in production mode, when they are updated frequently and a full Gitea restart each time is disruptive.