Skip to content

Build and publish managed releases in Daytona before deploying to the VPS #107

Description

@teckedd-code2save

Problem

Managed source deployments currently run docker compose build on the production VPS. Resource contention has interrupted GroundControl and RentAWeekend. GitHub Actions jobs are currently failing before steps start; PR #219 in RentAWeekend required a manual off-host artifact release. The user has requested a complete Daytona release path.

Delivery scope

  • Explicit per-deployment Daytona build policy with bounded resources, timeout, configured builder and GHCR destination.
  • Clone the linked repository at the exact requested commit using scoped GitHub access; never send runtime environments or application secrets to the builder.
  • Build the repository Dockerfiles in a disposable Daytona sandbox, publish revision-tagged images, and retain verified immutable digests.
  • GroundControl pulls and deploys those digests without building on the VPS, persists image overrides, verifies container health and the public endpoint, and rolls back failed replacement.
  • Connect merge-triggered durable operations and manual source deployment to the same path. Include progress, failure evidence and sandbox cleanup. No silent host-build fallback.
  • Preserve existing reproduction/repair functionality.

Acceptance

Unit/integration coverage of exact revision, unsupported Compose inputs, credential redaction, build/publish failure, cleanup, digest persistence and rollback; production build and relevant lint/tests. Prove remote build, registry push/read, deployment verification and rollback with a controlled workload before enabling RentAWeekend autopilot.

Refs #86 and #82. Keep current healthy production services running during implementation.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions