Improvements for new releases

Would be great, if we could polish the update experience to new releases a little bit.

In the web updater, clicking on the linked “changelog” directs me to
https://nextcloud.com/changelog/#31-0-8

which is funny since, even though the URL point to the 8 release, the webpage itself only has information regarding 7.

But also in CLI the update experience is not that great.
Since the CDNs still seem to be overwhelmed, the download takes forever at 500kbit/s.
That would not be that bad, if the download happened earlier. But now I am stuck at:

[✔] Check for expected files
[✔] Check for write permissions
[✔] Create backup
[ ] Downloading ...

with the instance is in maintenance mode.

If the download would be the first step, slow download speeds would at least not matter that much, since the instance is not in maintenance mode at this step.

Yes, the upgrade process could be improved. This has been discussed many times.

It is possible to manually download the Nextcloud ZIP file beforehand and then use it. However, it would be much easier if you could simply download it from mirror or use local. Perhaps this is now possible. It would cool to set it in config.php. Parameter could be an URL or a local path/filename combination. There is no risk to data integrity. Perhaps it would also relieve the download server.

It would also be nice if you could skip the backup when using the web updater. At CLI it is possible. This often leads to the process being interrupted. I do not need the backup function of Nextcloud. A simple option to disable the backup completely in config.php would help me. Then for updater.phar i also do not need the parameter for skip backup anymore. I can set it once at config.php.

Perhaps a few developers are reading this. Or someone who simply posts an issue.

1 Like

That seems to have been fixed in the meantime.

Agreed. The entire system is backed up in two offsite locations every three hours, so Nextcloud insisting on collecting huge piles of useless copies of its former self is not a good thing. I wise there was a way to switch that off permanently.

1 Like

Hi Folks,

did you open a feature request for the suggestions you made in this email thread?

Often no ticket no change.

2 Likes

No ticket no change
Ticket no change

1 Like
1 Like

For this issue:
A simple option to disable the backup completely in config.php would help me. Then for updater.phar i also do not need the parameter for skip backup anymore. I can set it once at config.php.
There is no ticket (yet).

1 Like

After searching for a while, I couldn’t find any issues. But I had discussed it before. I have now created an issue.

1 Like

Just wanted to add that @rakekniven provided a hint >>here<< that a new updater will be included in Nextcloud 32, which should support distributed downloads. That sounds like the main problem with the current updater — the slow downloads whenever a new version is released — might then finally be a thing of the past. :slight_smile:

Oh yes. I created that issue myself a year ago. Despite searching through my own issues, I couldn’t find it. Thanks @kesselb.

@kesselb
In another issue from yesterday:

  1. Regarding the updater backups: value to enable/disable upgrade-backup in config.php for updater.phar and web-updater updater#549. There’s no particular reason why I didn’t add the skip backup option to the web UI back then, apart from not using the web UI myself. It should be doable to add such a checkbox and/or a configuration flag. Feel free to send a pull request.

Must we create a pull request? Can you tell me what happens now?

This topic was automatically closed after 3 days. New replies are no longer allowed.

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.