Deployment, persistence and troubleshooting
Check actual origins, container networking, data volumes and health.
Default runtime
Compose provides core, portal and admin by default. SQLite stores business and authentication state, local stores media, and ordinary cache uses memory. Redis is enabled through an optional overlay. MySQL, object storage and external authentication providers are optional combinations, not CMS prerequisites. PostgreSQL application runtime is not complete.
Origins and networking
Browsers use public Portal/Admin origins; Portal servers use the internal Gateway URL. localhost inside a container points to itself, not another service. Public origins must agree with Cookie, callback and authorized-preview settings.
MF artifacts and service identity
Defaults initialize absent records and preserve saved choices/disablement. Browser artifacts use public /mf paths; Node uses private Core /_mosaic/mf/node, without a separate artifact service. Compose identities use separate read-only volumes; Zeabur consumers receive only their own derived identity. Never share the master key. Update saved browser entries and restart hosts after changing domains.
Diagnose by stage
- Unreachable page: check processes, mapped ports and frontend health.
- Unhealthy Core: inspect database connectivity and migration logs; do not enable synchronize.
- Write 403: inspect roles/project policies and configured origins, without weakening authorization.
- Missing image: inspect media volume, visibility, original URL and actual file bytes.
- Identity failure after rebuild: verify persistent data and original encryption/signing secrets rather than a different environment.
Separately qualified work
The standard containers, split MF, Notes and two local HTTPS origins have installation/rebuild acceptance. A real public Zeabur project, domains/provider callbacks, extra runtime combinations and the complete Public Build release are qualified separately. Full recovery, AI translation and same-page business microfrontends remain deferred. External projects use the developer kit and their own Dockerfile, with per-application identity, MF, persistence and acceptance.