Repository navigation
Add cloud deployment: published image, HTTPS stack and guide - #356
Merged
Merged
Conversation
Releases now push the validated image to ghcr.io/<owner>/agentloop with version and latest tags after checking it reports the release version as a non-root user. deploy/ provides a production Compose stack for one Linux server: Postgres, the API, the dashboard behind a Caddy login and automatic HTTPS, publishing only ports 80 and 443. A new CI job runs that stack over HTTPS and checks API key use, the HTTP redirect, the upload limit, the dashboard login and that internal ports stay unpublished. docs/CLOUD_DEPLOY.md covers single-server and managed platforms. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
AgentLoop replay self-testThis required repository check evaluates generated synthetic demo traces. It tests the replay and CI machinery; it does not show that this PR improves application performance. AgentLoop CI Report
Performance Gates
Trace inputsThis comparison includes synthetic data. It does not establish application performance gains from a pull request.
Metric Impact
Top Findings
|
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.
Makes running a shared AgentLoop server in the cloud a supported path.
Container image (release.yml): new `publish-image` job (needs guard + full validate) builds the Dockerfile from the tagged commit (official base via the mirror-fallback script), checks the image reports the release version and runs non-root, then pushes `ghcr.io//agentloop:X.Y.Z` and `:latest` with `GITHUB_TOKEN` (`packages: write` on that job only, Docker CLI only, no new third-party actions). Dockerfile gains OCI labels linking the package to the repo.
`deploy/` production stack: `docker-compose.yml` with Postgres, API, dashboard and Caddy; `Caddyfile` serving the API and the dashboard on separate HTTPS hostnames with automatic certificates, a bcrypt basic-auth login in front of the dashboard, HSTS/nosniff headers and an upload size limit; `.env.example` with every setting. Only 80/443 are published; image versions are pinned via `AGENTLOOP_IMAGE`.
CI (`deploy-stack` job): runs that exact stack with the commit's image over HTTPS using Caddy's local CA for `*.localhost`, and checks: `scripts/smoke_api.py` over HTTPS (API key creation, upload, report, list), HTTP→HTTPS 308, oversized upload → 413, dashboard 401 without/with wrong login and loads with the right one, and ports 8000/8501/5432 unpublished.
Docs: new `docs/CLOUD_DEPLOY.md` (single server on any cloud, API keys, upgrades/backups, managed platforms marked as not CI-tested, security checklist), mkdocs nav, README section, PRODUCTION and RELEASING notes (incl. the one-time step to make the GHCR package public), changelog.
Locally: pre-commit, `mkdocs build --strict` and workflow/docs/README tests pass. Docker is not available on the dev machine, so the stack itself is first exercised by the new CI job.
🤖 Generated with Claude Code