ops(rs2000-legacy): migrate edge utility config binds for CoreDNS, ntfy, searxng #552

Closed
opened 2026-05-28 01:37:55 +02:00 by codex · 1 comment
Collaborator

Scope

Move legacy config bind mounts for CoreDNS, ntfy, and searxng.

Observed legacy mounts

  • home-platform-coredns-1: /opt/vps-home-platform-infra/config/coredns/zones -> /etc/coredns/zones ro
  • home-platform-coredns-1: /opt/vps-home-platform-infra/config/coredns/Corefile -> /etc/coredns/Corefile ro
  • home-platform-ntfy-1: /opt/vps-home-platform-infra/config/ntfy/server.yml -> /etc/ntfy/server.yml ro
  • home-platform-searxng-1: /opt/vps-home-platform-infra/config/searxng/settings.yml -> /etc/searxng/settings.yml ro

Acceptance criteria

  • PR updates paths and docs for all three utilities or explains a safer split.
  • Runtime recreates are per-service and operator-approved.
  • Smoke covers DNS/ntfy/searxng health metadata only.
  • No config secret values are printed.
  • Legacy mount count decreases for CoreDNS, ntfy, and searxng.

Out of scope

  • DNS policy redesign.
  • ntfy auth changes.
  • searxng upgrade/settings refactor.

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 legacy config bind mounts for CoreDNS, ntfy, and searxng. ## Observed legacy mounts - `home-platform-coredns-1`: `/opt/vps-home-platform-infra/config/coredns/zones` -> `/etc/coredns/zones` ro - `home-platform-coredns-1`: `/opt/vps-home-platform-infra/config/coredns/Corefile` -> `/etc/coredns/Corefile` ro - `home-platform-ntfy-1`: `/opt/vps-home-platform-infra/config/ntfy/server.yml` -> `/etc/ntfy/server.yml` ro - `home-platform-searxng-1`: `/opt/vps-home-platform-infra/config/searxng/settings.yml` -> `/etc/searxng/settings.yml` ro ## Acceptance criteria - PR updates paths and docs for all three utilities or explains a safer split. - Runtime recreates are per-service and operator-approved. - Smoke covers DNS/ntfy/searxng health metadata only. - No config secret values are printed. - Legacy mount count decreases for CoreDNS, ntfy, and searxng. ## Out of scope - DNS policy redesign. - ntfy auth changes. - searxng upgrade/settings refactor. ## 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.
Author
Collaborator

Completed by PRs #583, #584, and #585. Ntfy, SearXNG, and CoreDNS config mounts now use /opt/pdurlej-platform/runtime/legacy-import; each runtime recreate was service-scoped; health/smoke checks were green and unhealthy count was 0.

Completed by PRs #583, #584, and #585. Ntfy, SearXNG, and CoreDNS config mounts now use `/opt/pdurlej-platform/runtime/legacy-import`; each runtime recreate was service-scoped; health/smoke checks were green and unhealthy count was 0.
codex closed this issue 2026-05-29 01:03:45 +02:00
Sign in to join this conversation.
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#552
No description provided.