Skip to content

Add self-contained Compose deployment templates - #375

Merged
RyanLee-Dev merged 4 commits into
mainfrom
codex/platform-deploy
Oct 1, 2026
Merged

RyanLee-Dev merged 4 commits into
mainfrom
codex/platform-deploy

Conversation

@RyanLee-Dev

@RyanLee-Dev RyanLee-Dev commented Oct 1, 2026 •

Copy link
Copy Markdown
Contributor

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_URL uses http://localhost:8080 so 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:

  • Eight focused Compose tests cover initialization, preserved secrets, missing-secret refusal, download integrity, platform network injection and unset/empty/explicit public URL interpolation.
  • CI planner/gate and measurement tests (47), configuration-reference validation, documentation checks (5), name tests (15), the name guard and actionlint 1.7.12 passed.
  • The required compose CI job runs scripts/compose-smoke.py on 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.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

@mintlify

mintlify Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
openagentcore 🟢 Ready View Preview Oct 1, 2026, 10:18 AM

💡 Tip: Enable Automations to automatically generate PRs for you.

@RyanLee-Dev
RyanLee-Dev merged commit 1f83546 into main Oct 1, 2026
26 checks passed

This branch was successfully deployed

1 active deployment
staging — 999a43bb Deployed Oct 1, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant