Add self-contained Compose deployment templates - #375
Merged
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Users can deploy the control plane from the published GHCR images with a self-contained Compose file. The template initializes random credentials and persistent volumes, runs database migrations before Core, and exposes the console and APIs through one gateway for the platform to route.
An unset or empty
OAC_PUBLIC_URLuseshttp://localhost:8080so services can start before a domain is assigned. Set the real HTTPS origin and redeploy Core and Web with the same volumes to enable platform-domain access; changing the environment does not update running processes.Compose template and test changes select the live smoke job alongside distribution fixtures; a failed, cancelled or unexpectedly skipped smoke fails the required
check. Each smoke uses a unique project and loopback port, with script cleanup and an additional always-run CI cleanup step.The change adds generic Compose and local access definitions, Dokploy template metadata, and Dokploy/Coolify import instructions. Images and node installation metadata are pinned to the same v0.0.3 release. Application code, Dockerfiles and release publication remain unchanged.
Validation:
composeCI job runsscripts/compose-smoke.pyon Linux with the real published images. It verifies empty-volume startup with no public URL, console sign-in, API authentication, a 5 MiB upload and the node installer checksum, then changes the URL and recreates containers while retaining keys, installation identity, project and file metadata. The script passed locally; credentials were absent from logs and its test resources were removed.Limits: no live Dokploy/Coolify deployment or runtime/model execution was tested. The local Docker host is arm64 running amd64 images; an earlier attempt hit a Core Go runtime fatal error (
found pointer to free object) and an HTTP 502, then recovered. The cause is unconfirmed; a subsequent complete smoke passed. First initialization downloads the approximately 385 MB control archive to extract node installation metadata. Platform imports still require domain/HTTPS setup; this PR does not publish a marketplace listing.Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.