pdurlej/platform

Fork 0

ops(rs2000-legacy): migrate Matrix/Synapse/Element bind mounts #545

New issue

Closed

opened 2026-05-28 01:37:53 +02:00 by codex · 2 comments

codex commented

2026-05-28 01:37:53 +02:00

Collaborator

Scope

Move Matrix-related legacy bind mounts off /opt/vps-home-platform-infra with backup/rollback evidence.

Observed legacy mounts

home-platform-synapse-1: /opt/vps-home-platform-infra/data/matrix/synapse -> /data rw
home-platform-element-web-1: /opt/vps-home-platform-infra/data/matrix/element/config.json -> /app/config.json rw
home-platform-matrix-well-known-1: /opt/vps-home-platform-infra/data/matrix/well-known -> /usr/share/nginx/html ro

Acceptance criteria

Backup/copy plan preserves data, ownership, modes, symlinks, timestamps.
PR updates only Matrix/Synapse/Element/well-known paths and docs.
Runtime approval is explicit and recreate is limited to affected Matrix services.
Smoke covers Synapse, Element config load, and well-known endpoint metadata.
Legacy mount count decreases for these services.

Out of scope

Synapse upgrade.
Matrix account/data migration beyond path move.
Changing Matrix public exposure.

Common safety rules

Recommended executor: Gemini 3.5 Flash local for repo/doc/plan work.
Do not delete, rename, prune, or edit /opt/vps-home-platform-infra in this issue.
Do not print secrets, env values, private messages, emails, or Iskra memory.
Runtime execution requires a separate explicit operator approval in the PR/issue thread.
First step is always read-only evidence refresh.
Preserve ownership, modes, symlinks, and timestamps when copying data/config.
Update compose/module docs through a PR before recreating affected services.
Recreate only affected service(s), never the whole platform, unless a later operator gate says otherwise.

## Scope Move Matrix-related legacy bind mounts off `/opt/vps-home-platform-infra` with backup/rollback evidence. ## Observed legacy mounts - `home-platform-synapse-1`: `/opt/vps-home-platform-infra/data/matrix/synapse` -> `/data` rw - `home-platform-element-web-1`: `/opt/vps-home-platform-infra/data/matrix/element/config.json` -> `/app/config.json` rw - `home-platform-matrix-well-known-1`: `/opt/vps-home-platform-infra/data/matrix/well-known` -> `/usr/share/nginx/html` ro ## Acceptance criteria - Backup/copy plan preserves data, ownership, modes, symlinks, timestamps. - PR updates only Matrix/Synapse/Element/well-known paths and docs. - Runtime approval is explicit and recreate is limited to affected Matrix services. - Smoke covers Synapse, Element config load, and well-known endpoint metadata. - Legacy mount count decreases for these services. ## Out of scope - Synapse upgrade. - Matrix account/data migration beyond path move. - Changing Matrix public exposure. ## Common safety rules - Recommended executor: Gemini 3.5 Flash local for repo/doc/plan work. - Do not delete, rename, prune, or edit `/opt/vps-home-platform-infra` in this issue. - Do not print secrets, env values, private messages, emails, or Iskra memory. - Runtime execution requires a separate explicit operator approval in the PR/issue thread. - First step is always read-only evidence refresh. - Preserve ownership, modes, symlinks, and timestamps when copying data/config. - Update compose/module docs through a PR before recreating affected services. - Recreate only affected service(s), never the whole platform, unless a later operator gate says otherwise.

codex added this to the 01 - RS2000 closeout and legacy cleanup milestone

2026-05-28 01:37:53 +02:00

codex added the

risk/exposure

ready-for-agent

risk/runtime

class/security-sensitive

labels

2026-05-28 01:37:53 +02:00

codex referenced this issue

2026-05-29 01:04:22 +02:00

ops(rs2000-legacy): refresh live bind-mount inventory before migration batches #543

codex commented

2026-05-29 01:05:24 +02:00

Author

Collaborator

Current evidence after PRs #583-#593:

remaining Matrix legacy mounts are now only:
- home-platform-synapse-1: /opt/vps-home-platform-infra/data/matrix/synapse -> /data
- home-platform-element-web-1: /opt/vps-home-platform-infra/data/matrix/element/config.json -> /app/config.json
matrix-well-known was completed by PR #586 and no longer has a legacy mount.
Docker labels show these containers came from old /opt/vps-home-platform-infra/compose/base,edge,core,apps config files; current release compose does not define synapse or element-web.

Next PR must either restore repo-owned desired-state definitions for Synapse/Element with legacy-import mounts, or explicitly retire/park them. Do not infer env/secrets from docker inspect alone.

Current evidence after PRs #583-#593: - remaining Matrix legacy mounts are now only: - `home-platform-synapse-1`: `/opt/vps-home-platform-infra/data/matrix/synapse` -> `/data` - `home-platform-element-web-1`: `/opt/vps-home-platform-infra/data/matrix/element/config.json` -> `/app/config.json` - `matrix-well-known` was completed by PR #586 and no longer has a legacy mount. - Docker labels show these containers came from old `/opt/vps-home-platform-infra/compose/base,edge,core,apps` config files; current release compose does not define `synapse` or `element-web`. Next PR must either restore repo-owned desired-state definitions for Synapse/Element with legacy-import mounts, or explicitly retire/park them. Do not infer env/secrets from `docker inspect` alone.

codex referenced this issue

2026-05-29 01:05:26 +02:00

ops(rs2000-legacy): validate zero legacy bind mounts and green smokes #556

codex commented

2026-05-29 01:48:38 +02:00

Author

Collaborator

Completed in the M01 orphan remount pass.

Runtime evidence:

home-platform-synapse-1 now mounts /data from /opt/pdurlej-platform/runtime/legacy-import/data/matrix/synapse.
home-platform-element-web-1 now mounts /app/config.json from /opt/pdurlej-platform/runtime/legacy-import/data/matrix/element/config.json.
Both containers recreated from Docker inspect snapshot via Docker API; env values were preserved in-memory and not printed.
Both containers ended running / healthy.
matrix-well-known was already completed by PR #586.

No source data/config was deleted.

Completed in the M01 orphan remount pass. Runtime evidence: - `home-platform-synapse-1` now mounts `/data` from `/opt/pdurlej-platform/runtime/legacy-import/data/matrix/synapse`. - `home-platform-element-web-1` now mounts `/app/config.json` from `/opt/pdurlej-platform/runtime/legacy-import/data/matrix/element/config.json`. - Both containers recreated from Docker inspect snapshot via Docker API; env values were preserved in-memory and not printed. - Both containers ended `running` / `healthy`. - `matrix-well-known` was already completed by PR #586. No source data/config was deleted.

codex closed this issue

2026-05-29 01:48:38 +02:00