Skip to content

Add cloud deployment: published image, HTTPS stack and guide - #356

Merged
dipeshbabu merged 1 commit into
mainfrom
feat/cloud-deploy
Nov 20, 2026
Merged

dipeshbabu merged 1 commit into
mainfrom
feat/cloud-deploy

Conversation

@dipeshbabu

Copy link
Copy Markdown
Owner

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

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>
@coderabbitai

coderabbitai Bot commented Nov 20, 2026

Copy link
Copy Markdown

Important

  • Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@github-actions

Copy link
Copy Markdown

AgentLoop replay self-test

This 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

  • Status: passed
  • Replay: Replay passed: latency improvement 69.67%, cost improvement 78.82%, retry delta -1.
  • Merge recommendation: synthetic self-test only; assess application traces before merge
  • Findings: 1 total, 0 high severity, 1 patchable

Performance Gates

Gate Status Detail
latency_regression pass 0.00% regression <= 0.00% allowed
cost_regression pass 0.00% regression <= 0.00% allowed
latency_improvement pass 69.67% improvement >= 20.00% required
cost_improvement pass 78.82% improvement >= 5.00% required
retry_non_increase pass 0 candidate retries <= 1 baseline retries

Trace inputs

This comparison includes synthetic data. It does not establish application performance gains from a pull request.

Side Run ID Path Synthetic marker Source
baseline run_3fc2e4de4dc1465b runs/research_agent_baseline.json yes agentloop_demo
candidate run_494b9c64081d411a runs/research_agent_optimized.json yes agentloop_demo

Metric Impact

Metric Impact
Latency improvement 69.67%
Cost improvement 78.82%
Retry delta -1
Candidate schema validity not provided
Candidate quality score not provided

Top Findings

Finding Severity Type Rewrite
al_cache_context_f6536e2bc19e: Cache repeated prompt/context prefix medium cache_context Move stable instructions into cached prefixes, summaries, or framework-level memory instead of resending full text.

@dipeshbabu
dipeshbabu merged commit 22b9bb6 into main Nov 20, 2026
26 checks passed
@dipeshbabu
dipeshbabu deleted the feat/cloud-deploy branch November 20, 2026 01:00
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