SLICE12 — Fresh-install setup-conductor.sh update

Status: Planned

Purpose

Update Skeleton Works' Conductor setup process to install the new standalone release and provide persistent installed-app storage.

Working instructions

Read CODEX.md and applicable AGENTS.md instructions before work. Current source and tests are authoritative. Preserve unrelated working-tree changes. Use this file as both the slice specification and its continuing log.

This slice is planned; do not start it as part of SLICE10. Update the checklist and append dated log entries as work proceeds. Record decisions, changed files, checks and results, failures, unresolved issues and the next action. Do not erase earlier log entries or claim VM/release acceptance from local tests alone.

Scope

Update /home/vwiebe/projects/skeletonworks-scripts/setup-conductor.sh to use the verified SLICE11 release.
Create/mount the persistent storage expected by the generic installed-app host.
Preserve customer URL discovery, Docker-based builds/runtime, persistent keys and existing first-run account setup.
Deliver favicon/title behavior through the Conductor release; do not patch frontend source from the setup script.
Keep Conductor mandatory in the SaaS offering while leaving Social Scheduler unregistered until its installer succeeds.
Give clear guidance for existing installations so fresh setup is not confused with the SLICE13 upgrade process.
Update installation and handover guides, including sudo for protected discovery/dry-run operations.

Acceptance checks

Action	Purpose / expected behavior
Run setup on a fresh customer-style VM	The selected release, default favicon, titles and management screens are present.
Inspect URLs, volumes and first-run setup	They match the customer setup result and persist after restart.
Open Publishing before and after app installation	No false app entry appears before its installer succeeds.
Install without host Node.js	The Docker-based installation works without adding Node to the VM.

Boundaries and dependencies

Depends on SLICE11. Preserve the earlier completed slices and their logs.

The customer control panel and other SaaS backlog items remain outside these four slices. The user reports only one live Conductor instance, which has Social Scheduler installed. A clean Conductor reset is an available fallback if a safe retrofit is impractical; first record the exact scope and backup/recovery plan. This does not authorize wiping the entire VM or deleting Node-RED's saved connections or PostgreSQL's schedules.

Progress log

2026-09-13 — Plan recorded

Renamed the proposed four phases to SLICE10, SLICE11, SLICE12 and SLICE13, respectively.
Implementation has not started.

Current handoff

Await completion of the preceding slice and the instruction to proceed.

2.9 KiB Raw Blame History