Skip to content
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

Maintenance/read-only mode #6020

Closed
burner1024 opened this issue May 15, 2021 · 4 comments
Closed

Maintenance/read-only mode #6020

burner1024 opened this issue May 15, 2021 · 4 comments
Labels
question This is more a question for the support than an issue. wontfix Nobody will work on this.

Comments

@burner1024
Copy link
Contributor

burner1024 commented May 15, 2021

Is your feature request related to a problem? If so, please describe.

I'd like to upgrade Weblate, however I'm concerned that users will access it during the upgrade and that'll interfere with upgrade process and/or result in a loss of work in case I need to roll back.

Describe the solution you'd like

Single-button lock down of all "write" actions for all users except admins. Display a custom note with some info.

Describe alternatives you've considered

I could lock it down by ip on webserver level, but that will not be as transparent, break badges on external sites in the meantime, etc.

Additional context

In fact, I'd be interested to know how you do it on https://hosted.weblate.org. Is it documented anywhere?

@nijel
Copy link
Member

nijel commented May 15, 2021

On Hosted Weblate we know what changes are being deployed (it is updated more frequently) and depending on that one of workflows is used:

  • In case of non-breaking changes, the app is kept running, upgraded and uwsgi restarted.
  • In case of bigger updates, the app is stopped, upgraded and then started.

For the second case we have web server configured in a way to display a maintenance message (which is here: https://github.com/WeblateOrg/wllegal/blob/main/wllegal/templates/weblate_50x.html).

@nijel
Copy link
Member

nijel commented May 15, 2021

The maintenance mode of Weblate would not address this in general - the database schema changes between versions and the old version is not be able to work with the new one.

@nijel nijel added the question This is more a question for the support than an issue. label May 15, 2021
@github-actions
Copy link

This issue looks more like a support question than an issue. We strive to answer these reasonably fast, but purchasing the support subscription is not only more responsible and faster for your business but also makes Weblate stronger. In case your question is already answered, making a donation is the right way to say thank you!

@github-actions
Copy link

This issue has been automatically marked as stale because there wasn’t any recent activity.

It will be closed soon if no further action occurs.

Thank you for your contributions!

@github-actions github-actions bot added the wontfix Nobody will work on this. label May 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question This is more a question for the support than an issue. wontfix Nobody will work on this.
Projects
None yet
Development

No branches or pull requests

2 participants