Practical self-hosting · beginner
09 · Who owns this application?
Compare platform-managed and standalone operation.
What you can take away
- Assign responsibility for updates, data and recovery.
- Create a responsibility table with rows for configuration, image updates, certificates, secrets, database migration, backups, and restores
Your trail through this idea
Checking saved progress…
A dashboard offers a convenient install button. A separate Compose file offers complete control. The useful comparison is who performs each operational responsibility after installation.
Prerequisite: complete the preceding lesson or bring its worksheet.
Understand the system
Ian’s past Runtipi-versus-standalone questions motivate this design lab; they do not establish which platform is running today. A management platform can supply application definitions, lifecycle controls, and conventions. A standalone project makes those choices more visible to its operator. Neither arrangement removes responsibility for backup, permissions, compatibility, or recovery.
Compose’s application model helps reveal the underlying units regardless of the interface used to manage them. Avoid mixing two managers over the same resources unless their documented integration explicitly supports it. Otherwise each may attempt to restore its own idea of the desired configuration.
Work through the case
Original exercise: a platform recreates an application from its stored definition, while an operator manually edits the generated Compose file. The edit works until the next platform action replaces it. This is a hypothetical ownership conflict, not a report of a specific Runtipi defect. The lesson is to locate the authoritative configuration and supported customization mechanism.
Make something useful
Try this
Original exercise
Create a responsibility table with rows for configuration, image updates, certificates, secrets, database migration, backups, and restores. Fill two columns: managed platform and standalone. Mark each entry as verified, assumed, or unknown. Use the documentation for the exact installed version before any migration. Do not move a real application for this lab; instead draft an export and rollback checklist.
Check your reasoning
A quick check · for your own learning
Why identify the authoritative configuration?
A self-study prompt. You can retry; this is not an exam.
Keep the result and follow the sources
A successful comparison names tradeoffs you can test. A migration proposal must include data ownership and a way back, not just screenshots of the new dashboard. Keep unknown platform-specific behavior explicit until verified.
Sources and scope
- Primary documentation or archival source, reviewed 14 November 2026. Additional direct links appear beside the claims they support.
- Editorial basis: Ian's historical self-hosting questions and current repository inspection informed the case selection. Historical requests do not establish current deployment. Private chat records, credentials and host details are excluded.
- Examples and exercises are original educational synthesis. External sources support the stated technical or historical context, not every hypothetical scenario.