Create and build a Blueprint.
Starts build of custom defined container Blueprint. The Blueprint will begin in the ‘provisioning’ step and transition to the ‘building’ step once it is selected off the build queue., Upon build complete it will transition to ‘building_complete’ if the build is successful.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
Name of the Blueprint.
A list of code mounts to be included in the Blueprint.
Dockerfile contents to be used to build the Blueprint.
(Optional) Map of paths and file contents to write before setup..
Parameters to configure your Devbox at launch time.
A list of commands to run to set up your system.
Response
Blueprints are ways to create customized starting points for Devboxes. They allow you to define custom starting points for Devboxes such that environment set up can be cached to improve Devbox boot times.
Creation time of the Blueprint (Unix timestamp milliseconds).
The id of the Blueprint.
The name of the Blueprint.
The parameters used to create Blueprint.
The status of the Blueprint build.
provisioning, building, failed, build_complete The failure reason if the Blueprint build failed, if any.
out_of_memory, out_of_disk, build_failed Was this page helpful?