diff options
| author | mail_redacted_for_web | 2026-03-08 16:00:15 +0100 |
|---|---|---|
| committer | mail_redacted_for_web | 2026-03-08 16:00:15 +0100 |
| commit | 6bda904e94f6f8bb5dfa6290d2f2470ff261ae1f (patch) | |
| tree | e1633bfcc381eb4c0d8d856a3196886f75847a6e | |
| parent | 5b4ce599b291cd446dae4a2940f3cf1f7b7d6483 (diff) | |
| download | nextcloud-update-6bda904e94f6f8bb5dfa6290d2f2470ff261ae1f.tar.bz2 | |
doc: + remark about rollbacks
| -rw-r--r-- | README.md | 4 |
1 files changed, 3 insertions, 1 deletions
@@ -15,7 +15,9 @@ updater.phar is useless. by the web server user (utterly insane!), we don't want to rely on such a construct too much. (Nextcloud don't give a fuck about security principles that are aaaaages old? Fuck your meta layers, then, we don't trust you anymore. Security fucked once, security fucked always.) -4. Solution? Create own scripts which take over downloads, download verification, and then +4. Also, it rolls back everything on any failure - including downloads which will be fully + re-executed, every. single. time. +5. Solution? Create own scripts which take over downloads, download verification, and then execute occ commands (well, they're still occ commands, but more granular and potentially less fucked by imbecile decisions). |