feat: oc11 to support docker only deployments

[DeepDiver1975]

No description provided.

[DeepDiver1975]

PR Review — feat: oc11 to support docker-only deployments

Status: DRAFT | +2248 / -1733

---

Overview

This PR migrates all ownCloud Server documentation to assume a Docker-only deployment model. It:

• Renames/replaces the occ-command-example-prefix attribute with occ-command-example-prefix-docker (resolved as docker compose exec owncloud occ)
• Rewrites the occ_command.adoc intro section to focus entirely on Docker
• Updates docker-compose.yml with several structural improvements (named networks, variable-driven image tags, long-form volume syntax)
• Deletes the command-line installation commands doc
• Adds a NOTE: Run this command inside the ownCloud Docker container. after every single occ code block

---

Issues & Concerns

Security — High

• Exposed database and cache ports in docker-compose.yml: Ports 3306 and 6379 are now published to the host. By default Docker binds these to 0.0.0.0, making MariaDB and Redis reachable from outside the host. For a documentation/example compose file that new users copy-paste, this is a serious security footgun. These services communicate only within oc_network and do not need host-level port bindings.

---

Breaking Changes — Should Be Documented

• Volume renamed from files to oc_files: Any existing user following the prior guide and then pulling this update will have orphaned data in the old files volume. A migration note or upgrade warning is needed.

• Env var OWNCLOUD_VERSION → OWNCLOUD_IMAGE: Existing .env files will silently fail because the variable name changed. Either keep backward compatibility or explicitly call out this rename in an upgrade notice.

• Page aliases removed from occ_command.adoc: The large :page-aliases: block (covering ~30 paths) was deleted entirely. These aliases exist specifically to keep old bookmarks and cross-references alive. Removing them will break every inbound link from the published site and other docs repos that reference those paths.

---

Documentation Quality

• Repetitive notes: The phrase NOTE: Run this command inside the ownCloud Docker container. appears after every single code block — more than 100 times across the diff. This creates significant noise. A single note at the top of the occ_command.adoc "Running occ" section (and possibly a short admonition box at the top of frequently-used sub-pages) would communicate the same information far more cleanly. Repeating it per-command suggests the docs were mechanically transformed rather than deliberately revised.

• [source,docker] is non-standard: AsciiDoc/Antora does not recognise docker as a syntax-highlighting language identifier. Use [source,bash,subs="attributes+"] (as was done previously) or [source,console,subs="attributes+"] to get consistent rendering.

• Version mismatch in examples: The example occ status output now shows 11.0.0, but latest-server-version in global-attributes.yml is still 10.15. Either update both or keep the examples at the current release version to avoid confusing readers.

---

Structural / Correctness

• Healthcheck removed from ownCloud service: The previous compose file used the ownCloud healthcheck as a depends_on condition target. Removing it without checking whether anything downstream still references it could silently break container orchestration ordering. Verify whether depends_on: condition: service_healthy is still used anywhere in the compose or docs for this service.

• Inconsistent volume definitions: oc_files uses the detailed long-form syntax with a bind-mount template comment, but mysql and redis still use the terse short form. Apply a consistent style across all three.

• Deleted _command_line_installation_commands.adoc: The maintenance:install command is useful for advanced scenarios (CI/CD, bare-metal fallback). Removing the doc entirely (rather than moving it to a "legacy" or "advanced" section) discards that content. Check whether the alias pointing to it is also gone from occ_command.adoc — it was in the page-aliases block that was deleted.

• SELinux references silently removed: configuration.adoc and harden_server.adoc had links to selinux_configuration.adoc that were stripped without explanation. If Docker removes the SELinux requirement, that should be stated explicitly; if the docs still apply, the links should stay.

---

Summary

The direction is correct for a Docker-first docs strategy, but the PR has three items that need to be resolved before merging:

1. Remove the exposed 3306/6379 host port bindings — they are a security risk for copy-paste users.
2. Restore the page aliases in occ_command.adoc or explicitly redirect them — removing them silently breaks published URLs.
3. Reduce the repetitive Docker container notes to a single per-page or per-section admonition.

The version mismatch (11.0.0 vs 10.15) and the breaking env-var / volume renames also need either updates or explicit migration guidance before this is ready to merge.

🤖 Review generated with Claude Code

[mmattel]

If we need it again to find and replace multi line patterns (Claude issue):
find . -type f -name '*.adoc' -exec sed -i -z -E 's|\nNOTE: Run this command inside the ownCloud Docker container.\n||gm' '{}' \;