fix(cutover): remount dashboard and searxng config imports #584

Merged
pdurlej merged 1 commit from codex/m01-remount-dashboard-searxng-config into main 2026-05-29 00:06:17 +02:00
Collaborator

Canary status: missing — fire canary 3+3 manually before merge

Summary

Second M01 config-only remount batch after ntfy proved the pattern at runtime.

This PR moves default config bind mounts for two non-core tailnet services to prepared legacy-import paths:

  • dashboard: /opt/pdurlej-platform/runtime/legacy-import/config/homepage
  • searxng: /opt/pdurlej-platform/runtime/legacy-import/config/searxng/settings.yml

Both old legacy paths remain available as explicit rollback env vars for one rollback cycle.

Canary Context Pack

Product story

M01 needs active services to stop depending on /opt/vps-home-platform-infra before quarantine/destructive cleanup. dashboard and searxng are small config-only candidates with healthchecks and clear rollback paths.

What changed

  • compose/apps/compose.yaml: default bind mounts for dashboard and searxng now point at copied legacy-import config paths.
  • modules/dashboard/runbook.md: documents config source and rollback env var.
  • modules/searxng/runbook.md: documents settings source and rollback env var.

Why it changed

The legacy root must stop being the default runtime source. This keeps old paths as rollback material while making the canonical release root independent of the legacy project tree.

Files touched

  • compose/apps/compose.yaml
  • modules/dashboard/runbook.md
  • modules/searxng/runbook.md

Relevant context

  • M01 RS2000 closeout critical path
  • ntfy remount was applied and reached healthy runtime state
  • Prior legacy import helper PRs

Runtime evidence

Prep copy already run on RS2000 before this PR:

scripts/cutover/prepare-legacy-import.sh --dry-run --path config/homepage
scripts/cutover/prepare-legacy-import.sh --yes --path config/homepage
target_size 136K /opt/pdurlej-platform/runtime/legacy-import/config/homepage

scripts/cutover/prepare-legacy-import.sh --dry-run --path config/searxng/settings.yml
scripts/cutover/prepare-legacy-import.sh --yes --path config/searxng/settings.yml
target_mode=644 target_size=150 /opt/pdurlej-platform/runtime/legacy-import/config/searxng/settings.yml

No service restart was performed for this PR.

Known constraints

  • This does not delete or quarantine legacy paths.
  • This does not migrate searxng_data or any other data volume.
  • This does not recreate containers before merge.

Explicit out-of-scope

  • data migration
  • service restart before merge
  • destructive cleanup
  • quarantine/tombstone
  • core DNS/Traefik/Matrix remounts

Requested decision

Approve this as the next config-only remount batch if checks are green.

Merge blockers

  • copied config targets missing on RS2000
  • compose syntax failure
  • reviewer finds a runtime fallback risk not covered by rollback env vars

Validation

  • git diff --check: passed
  • PYTHONPATH=control-plane uv run --project control-plane python -m platformctl.cli validate all --json: passed, exit 0

Spec sources read

  • compose/apps/compose.yaml — mount declarations
  • modules/dashboard/runbook.md — operator rollback/runbook update
  • modules/searxng/runbook.md — operator rollback/runbook update

Non-goals

No DB, no service, no webhooks, no issue/comment mutation, no destructive cleanup.

Canary status: missing — fire canary 3+3 manually before merge ## Summary Second M01 config-only remount batch after `ntfy` proved the pattern at runtime. This PR moves default config bind mounts for two non-core tailnet services to prepared `legacy-import` paths: - `dashboard`: `/opt/pdurlej-platform/runtime/legacy-import/config/homepage` - `searxng`: `/opt/pdurlej-platform/runtime/legacy-import/config/searxng/settings.yml` Both old legacy paths remain available as explicit rollback env vars for one rollback cycle. ## Canary Context Pack ### Product story M01 needs active services to stop depending on `/opt/vps-home-platform-infra` before quarantine/destructive cleanup. `dashboard` and `searxng` are small config-only candidates with healthchecks and clear rollback paths. ### What changed - `compose/apps/compose.yaml`: default bind mounts for `dashboard` and `searxng` now point at copied `legacy-import` config paths. - `modules/dashboard/runbook.md`: documents config source and rollback env var. - `modules/searxng/runbook.md`: documents settings source and rollback env var. ### Why it changed The legacy root must stop being the default runtime source. This keeps old paths as rollback material while making the canonical release root independent of the legacy project tree. ### Files touched - `compose/apps/compose.yaml` - `modules/dashboard/runbook.md` - `modules/searxng/runbook.md` ### Relevant context - M01 RS2000 closeout critical path - `ntfy` remount was applied and reached healthy runtime state - Prior legacy import helper PRs ### Runtime evidence Prep copy already run on RS2000 before this PR: ```text scripts/cutover/prepare-legacy-import.sh --dry-run --path config/homepage scripts/cutover/prepare-legacy-import.sh --yes --path config/homepage target_size 136K /opt/pdurlej-platform/runtime/legacy-import/config/homepage scripts/cutover/prepare-legacy-import.sh --dry-run --path config/searxng/settings.yml scripts/cutover/prepare-legacy-import.sh --yes --path config/searxng/settings.yml target_mode=644 target_size=150 /opt/pdurlej-platform/runtime/legacy-import/config/searxng/settings.yml ``` No service restart was performed for this PR. ### Known constraints - This does not delete or quarantine legacy paths. - This does not migrate `searxng_data` or any other data volume. - This does not recreate containers before merge. ### Explicit out-of-scope - data migration - service restart before merge - destructive cleanup - quarantine/tombstone - core DNS/Traefik/Matrix remounts ### Requested decision Approve this as the next config-only remount batch if checks are green. ### Merge blockers - copied config targets missing on RS2000 - compose syntax failure - reviewer finds a runtime fallback risk not covered by rollback env vars ## Validation - `git diff --check`: passed - `PYTHONPATH=control-plane uv run --project control-plane python -m platformctl.cli validate all --json`: passed, exit 0 ## Spec sources read - `compose/apps/compose.yaml` — mount declarations - `modules/dashboard/runbook.md` — operator rollback/runbook update - `modules/searxng/runbook.md` — operator rollback/runbook update ## Non-goals No DB, no service, no webhooks, no issue/comment mutation, no destructive cleanup.
fix(cutover): remount dashboard and searxng config imports
Some checks failed
canary-required / collect-diff (pull_request) Successful in 4s
platformctl plan / auto-apply scope (pull_request) Successful in 21s
patchwarden-client-dry-run / collect-diff (pull_request) Successful in 5s
base-is-main / guard (pull_request) Successful in 1s
patchwarden-pr-sanity / sanity (pull_request) Failing after 51s
patchwarden-pr-sanity / collect-diff (pull_request) Successful in 5s
canary-required / canary (pull_request) Has been skipped
patchwarden-client-dry-run / dry-run (pull_request) Successful in 20s
6f69161750
pdurlej deleted branch codex/m01-remount-dashboard-searxng-config 2026-05-29 00:06:17 +02:00
Sign in to join this conversation.
No reviewers
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/platform!584
No description provided.