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

Updater should make a backup of all files before replacing to allow easy rollback #13759

Open
Findus23 opened this issue Nov 24, 2018 · 0 comments
Labels
c: Usability For issues that let users achieve a defined goal more effectively or efficiently.

Comments

@Findus23
Copy link
Member

Findus23 commented Nov 24, 2018

This is just a basic idea, I am not sure how useful it is or how easy it is to implement.


I just updated Nextcloud and took a look at the upgrade screen (which nicely ticks one step after another after it is done)
grafik

(The procedure is also described at https://docs.nextcloud.com/server/13/admin_manual/maintenance/update.html)

I noticed that Nextcloud seems to backup it's files before the update. Maybe doing that would help get back to a working state in case Matomo is completly broken after an update (e.g. because of missing Classes or corrupted files which seems to be reported quite often)

Of course we would need to find a way to do the rollback (as the web ui is probably already broken at this point) and it wouldn't help if the database migration have already happened (but that would only happen in the next step).

@Findus23 Findus23 added the c: Usability For issues that let users achieve a defined goal more effectively or efficiently. label Nov 24, 2018
@mattab mattab added this to the Backlog (Help wanted) milestone Jan 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: Usability For issues that let users achieve a defined goal more effectively or efficiently.
Projects
None yet
Development

No branches or pull requests

2 participants