Practical self-hosting · beginner
10 · Two applications, one host, no accidental roommates
Understand project namespaces and deliberately shared resources.
What you can take away
- Design two isolated Compose projects with one intentional connection.
- On paper, design two practice projects
Your trail through this idea
Checking saved progress…
Two copies of a service need to run on the same machine. Their YAML files look independent, yet a volume or network unexpectedly overlaps. Names are part of the isolation boundary.
Prerequisite: complete the preceding lesson or bring its worksheet.
Understand the system
Compose project names group resources for an application instance. Project naming allows separate environments to use the same service definitions. Explicit external resources or fixed names can cross that boundary. Published host ports are another shared resource: two services cannot independently claim the same host address and port at the same time.
A safe design distinguishes intentional sharing from accidental collision. A reverse proxy may deliberately connect to multiple application networks; unrelated databases usually do not need that same connectivity. Shared resources need a named owner and a deletion policy.
Work through the case
Original example: lesson-a and lesson-b each contain a web service and a database. Their service names can match while project-scoped resources remain distinct. If both refer to the same explicitly external data volume, the project names alone no longer protect the data. Naming is a useful tool, not a universal guarantee.
Make something useful
Try this
Original exercise
On paper, design two practice projects. Give each a project name, database volume, internal network, and distinct optional host port. Then add exactly one shared reverse-proxy connection and explain why it exists. Review any external resources and fixed container names. Do not start a second copy of a production database against an existing volume.
Check your reasoning
A quick check · for your own learning
Can two project names guarantee isolation of an explicitly shared volume?
A self-study prompt. You can retry; this is not an exam.
Keep the result and follow the sources
Your deliverable is a resource-ownership map. Before removing an application, use it to identify what belongs to that project and what other services still depend on. Isolation should be evident before the cleanup command is considered.
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.