Quick Start¶
Go from zero to a live deployment in five steps. This guide assumes you have
the konigle CLI installed and a project API key ready.
Prerequisites
konigleCLI installed — see Installation- An active Konigle project with an API key
- A directory containing the app you want to deploy
Step 1 — Provision a computer¶
A computer is the VM that will run your app. Create one and wait for it to be ready:
The CLI waits until the computer is ready (usually 2–3 minutes) and prints a confirmation. You can list your computers at any time:
Step 2 — Create a web app¶
Create a web app on the computer you just provisioned. Replace my-server with
the name shown in computer list:
konigle cloud webapp create \
--computer my-server \
--name my-app \
--runtime python3 \
--database postgres \
--cache redis
This creates the web app and automatically provisions two spaces: uat and
production. The platform subdomains for your app are printed on completion.
Step 3 — Link your directory¶
From the directory you want to deploy, run:
This writes a .bentocloud.json file in the current directory so you don't
have to pass --computer, --webapp on every deploy.
Tip
Add .bentocloud.json to your .gitignore — it contains environment-specific
settings that shouldn't be committed.
Step 4 — Deploy¶
From the linked directory:
The CLI packages your code into a ZIP, uploads it to the uat space, and waits
for the build to finish. When it's done you'll see the uat URL
(my-app-uat.hostbento.app) where you can verify your app.
Note
You can only deploy to uat. To release to production, use promote in
the next step.
Step 5 — Promote to production¶
Once you're happy with what's running on uat:
This copies the live uat image to production — no re-upload or rebuild.
Your app is now live on the production URL.
What's next¶
- The Basics — understand Computers, Web Apps, and Spaces in depth
- CLI Reference — full options for every command