Skip to content

Add user-owned VPS deployment path - #2

Draft
unix2dos wants to merge 8 commits into
mainfrom
codex/carry-vps
Draft

unix2dos wants to merge 8 commits into
mainfrom
codex/carry-vps

Conversation

@unix2dos

Copy link
Copy Markdown
Owner

Scope

  • Add a single-host VPS deployment path using an existing SSH alias, local Docker build, image transfer, and Docker Compose with Caddy HTTPS.
  • Reuse Carry operation records for publish, reconciliation, logs, source rebinding, non-secret environment updates, and image-only rollback.
  • Update the product direction and record the first Loop → DMIT acceptance evidence.

Verification

  • go test -race ./cmd/carry, go vet ./cmd/carry, node --check cmd/carry/web/app.js passed.
  • Real DMIT publish, HTTPS health, anonymous Loop model/tool run, persistent-volume readback, and image rollback/restore passed; see validation/VPS-RESULTS.md for scope and limits.

Boundaries

  • One Carry-managed app per VPS in this preview. Databases, object storage, multi-app proxy routing, and full-server recovery remain outside this change.
  • The released Alpha installer still covers existing Vercel/Railway applications; this branch is the source preview.

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