diff options
| author | mail_redacted_for_web | 2026-03-07 11:16:36 +0100 |
|---|---|---|
| committer | mail_redacted_for_web | 2026-03-07 11:16:36 +0100 |
| commit | 616a5170903f85aceea3cd600650fcfbd13b54b4 (patch) | |
| tree | f0033d1964df0471a1b37940e7cb3269f3685d97 | |
| parent | 05f529061606d7c7ab94e390074526256079815b (diff) | |
| download | nextcloud-update-616a5170903f85aceea3cd600650fcfbd13b54b4.tar.bz2 | |
todos
| -rw-r--r-- | README.md | 5 |
1 files changed, 4 insertions, 1 deletions
@@ -33,13 +33,16 @@ updater.phar is useless. ## To-Dos 1. Finallise app-update sections once we have apps available for update to parse `update:check` output 2. See 1. under "State of Things" -3. Kind of related to 2. - we still need to build a package and make the script calls independent +3. Kind of related to 2. - we still need to build OS packages and make the script calls independent of /usr/local/bin 4. Maybe move anything except nextcloud-update to a "lib dir" - the scripts should be executable on their own, but the main idea is "call stuff and let the script decide what to do" 5. Make the current verbose output dependent on a CLI option, choose to also offer syslog and scheduler friendly output (i.e. only hard results on output for e.g. systemd timers, and ofc to logger) +6. On out Nextcloud 32.0.6 update, the bookmarks app rendered the upgrade unusuable due to duplicate + database entries. Not so hard to resolve eventually, but: find out whether we can add additional + error handling and/or messages for a case where an app kills off our upgrade process. # Footnotes |
