7.0
Attention! This is a release with breaking changes. Create a backup of your data before upgrading! Migrated data is not compatible with earlier versions of S3 Ninja!
If you encounter any issues, including conditions such as wrong sorting order, please get in touch.
- Bucket name rules are now enforced strictly. In particular, bucket names need to have between 3 and 63 characters. They must consist of numbers, lower-case letters, dots and hyphens, and the first and last character need to be a letter or a digit. Upper-case letters, spaces and other characters are not legal.
- Legacy buckets with illegal names are hidden. In order to show them again, rename the respective folders manually.
- To do so within a Docker environment, obtain the container name via
and obtain a shell:
docker ps
docker exec -it <container name> /bin/bash
- Object keys can now contain arbitrary UTF-8 characters, including slashes. In order to support this, data storage on disk was changed. The system attempts to migrate existing buckets automatically.
- If your object keys used to contain forward slashes (
/
), automatic migration will yield a file name with underscores, due to an erroneous legacy coding scheme.
- If your object keys used to contain forward slashes (
- URLs in the UI (accessible via
/ui
) have been adapted. - Faulty output when querying ACLs of non-existing buckets has been fixed.
- Deletion of non-existing buckets leads to a 404 error now.