Upload a Dockerfile build context (gzip tarball)
Used by the Dockerfile-via-tarball deploy mode. Send the gzipped tar of your project as the raw request body. The response returns a context_id you reference in a follow-up POST /platform/deployments/custom body.
Maximum 100 MiB per context (operator may lower). Default quotas are 10 unexpired/referenced uploads and 300 MiB per account. Referenced retained sources count toward quota. Quota exhaustion returns 429. Without retain=true, uploads remain temporary, one-use, with a 24-hour default TTL. With retain=true, an archive remains while an app references it; otherwise expires seven days after upload or last deployment request (not after detachment). The sweep removes file and row. Immutable IDs and SHA256 identify source bytes, not mutable build dependencies. See https://docs.imprezahost.com/source-uploads.html.
The CLI (impreza deploy) automates this two-step flow and bakes in a default exclude list (.git, node_modules, __pycache__, .venv, vendor, .impreza, *.pyc, .DS_Store).
Request
- Base URL: https://api.imprezahost.com/v1
- URL: https://api.imprezahost.com/v1/platform/deployments/custom/contexts
- Auth: API key in header X-API-Key and API key in header X-API-Secret
Query parameters
Opt in to retained source versions reusable for deployment and redeploy.
Optional UTF-8 label up to 120 bytes, without control characters.
Response
Context staged on disk
Changes
No recorded changes to this operation across all 1 revision of this API.