- Unify the different installation options available to users and presents them as a simple list
- Adds AIO link
- Adds community Docker link
Accomplishes this without changing documentation chapters/sections (so no external links break)
No changes to which approaches are "recommended"
Signed-off-by: Josh Richards <josh.t.richards@gmail.com>
When the command is started in maintenance mode it will even err out.
Also one should not disable encryption without decrypting all files first.
Signed-off-by: Max <max@nextcloud.com>
typo in the documentation.
actual command is encryption:fix-encrypted-version and not encryption:fix-encrypted-versionS
Signed-off-by: Maxime LE HERICY <87175513+maximelehericy@users.noreply.github.com>
The `--option=value` version of passing options to the `occ maintenance:install` command is now used in the documentation, instead of the `--option value` variant. This solves issues with leading dashes in values, especially passwords. It also matches the `occ help maintenance:install` output.
Solves:
- https://github.com/nextcloud/server/issues/26109
- https://github.com/nextcloud/documentation/issues/8190
Furthermore values are now single quoted, which is important to avoid variable expansion and special treatment of the backlash character in random passwords, and a doubled space was removed.
Signed-off-by: MichaIng <micha@dietpi.com>
After running into the problem myself and searching online for a solution i think a clarification on how to ensure proper permissions on the redis socket would be helpful to novice administrators
Added information about misplaced encryption keys and how to repair them
automatically or manually when needed.
Signed-off-by: Vincent Petry <vincent@nextcloud.com>
… in reverse_proxy_configuration.rst
While the rewrite rules should work I guess, they still trigger a warning
on the admin page. Using 301 redirects make the warning go away.
Signed-off-by: rusty-snake <41237666+rusty-snake@users.noreply.github.com>
Since Nextcloud 24 (nextcloud/server#e49233a79546) ROW_FORMAT is no
longer set to "COMPRESSED" when changing the character set of tables to
"utf8mb4" in the "Repair MySQL collation" repair step. However, that
repair step still sets the ROW_FORMAT to "DYNAMIC" before changing the
collation of tables, no matter the character set.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
For me personally, it took some time to figure out where to make these changes, I wish a line explicitly point out where and how to make those changes. I hope this commit does that.
Signed-off-by: pravynandas <pravynandas@users.noreply.github.com>
