diff --git a/CHANGELOG.md b/CHANGELOG.md index e4db1a7..40b80a9 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -7,6 +7,21 @@ the app store accepts a `-beta` suffix, but Nextcloud servers then only offer th beta/daily update channel, which would hide the app from most admins. The stability stage is instead carried by the app description, the git tag, the release, and this file. +## [Unreleased] + +### Fixed +- A full restore onto MySQL/MariaDB stopped with "Incorrect string value" when it created a table + (of an app that is not installed here) whose rows hold emoji or other 4-byte characters: the + table got 3-byte utf8. Tables the restore creates now get this installation's character set and + collation (utf8mb4). Found in a disaster recovery simulation onto MariaDB. + +### Changed +- README: a roadmap, the tested disaster recoveries, measurements for OVH S3, the Storage Box over + SFTP and SMB, how to build the SMB extension when PECL is down, and what works without shell + access. The guide lists shell access among what you need. +- The full-restore integration test checks a 4-byte character in a table the restore creates, and + retries app installs from the app store. + ## [1.0.0-rc.5] - 2026-10-22 Fifth release candidate for 1.0.0; the app version is 0.9.11. A full restore of 1 TB over SFTP diff --git a/README.md b/README.md index fd80c40..b4fa82d 100644 --- a/README.md +++ b/README.md @@ -265,7 +265,7 @@ a 👍 on its issue helps decide what comes first. system cron, with how to set one up. Without cron, a backup started with "Back up now" moves on while the NG Backup page is open ([#13](https://github.com/dillardblom/ng_backup/issues/13)). - An optional label for a backup started with "Back up now". -- Faster full restores from S3, reading ahead as restores over SFTP do since 1.0.0-rc.4. +- Faster full restores from S3 and SMB, reading ahead as restores over SFTP do since 1.0.0-rc.4. **1.1.0** - Restore without the recovery kit: the backup key from the location itself, opened with one of @@ -278,7 +278,9 @@ a 👍 on its issue helps decide what comes first. - Faster backups: reading and uploading at the same time. **Later** -- A full restore onto the existing installation, without first installing a fresh Nextcloud. +- A full restore onto the existing installation, without first installing a fresh Nextcloud, in a + restore mode of its own instead of maintenance mode, so that it can also run from the web + interface (for hosted Nextcloud without shell access). - Users restoring their own files from the Files app. - Primary object storage and External Storage mounts (see Known limitations). - An option not to keep the backup key on the location (the recovery kit is then the only copy).