feat(deploy): git-push deploy — the Vercel/Heroku ergonomic, sovereign (Cloud Native Buildpacks) - #33
Merged
Merged
Conversation
…n (Cloud Native Buildpacks)
Vercel and Heroku are the same move: detect the app from source, build it into a runnable image
WITHOUT a Dockerfile, deploy it, preview per branch. This delivers that sovereign + open.
tools/buildpack.py:
- detect(): which Paketo buildpack matches the source (requirements.txt/package.json/go.mod/
Cargo.toml/index.html) — no Dockerfile.
- build_plan(): CNB `pack build` model — detect -> reproducible OCI image (content-addressed over
source+buildpack; same source -> same image) + Procfile-style process_types + the real pack
command. Fail-closed: no match -> refuse, don't guess.
- deploy_workload(): the built image -> a workload the executor dispatches (service=Deployment,
worker=Job); the sandbox is the per-branch preview, the promotion gate is dev->prod. Verified the
built image flows into the k8s manifest.
docs/BUILD_DEPLOY.md articulates the full Vercel/Heroku -> continuum mapping: buildpack (this) + slug
= data sphere + Procfile = process_types + dyno = executor + preview = Signadot sandbox + pipeline =
promotion gate + tiers = admission. The sovereign version: reproducible+attestable build, OUR runtime
(incl. sovereign GPU inference), OUR residency-fenced data. capd/git-push-deploy.mesh.capd.json.
Tests: +5 = 162 tools tests green. The only remaining piece is the push trigger (webhook).
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
1 participant
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.
Vercel and Heroku are the same move — detect the app from source, build it into a runnable image without a Dockerfile, deploy it, preview per branch. This delivers that ergonomic sovereign and open, via Cloud Native Buildpacks / Paketo.
tools/buildpack.py:detect(no Dockerfile) →build_plan(pack build, reproducible content-addressed OCI image + Procfile-style process types, fail-closed on no match) →deploy_workload(the built image → an executor workload; sandbox = per-branch preview; promotion gate = dev→prod). Verified the built image flows into the k8s manifest.docs/BUILD_DEPLOY.mdmaps the whole thing: buildpack + slug=data sphere + Procfile=process_types + dyno=executor + preview=Signadot sandbox + pipeline=promotion gate + tiers=admission. The sovereign version — reproducible+attestable build, our runtime (incl. sovereign GPU inference), our residency-fenced data.162 tools tests green. Only the push trigger (webhook) remains.