Skip to main content
A deployment starts with a plan built from the project’s source. The plan lists the resources, provider accounts, regions and environment variables before Hoista changes anything. Connect the target account first.

From Desktop

Desktop has no deploy form. Ask a connected agent to deploy, for example “Deploy this project with Hoista”, or use the CLI below. Deploys in the sidebar shows every deploy as it runs, and a project’s Deploys tab shows that project’s history. For a watched project, the provider still runs the build. Use Deploy newest commit, or a row’s menu to redeploy, restart or roll back. Hoista asks the provider to do it.

Create and review a plan

Check the detected framework, resource names, accounts, regions, required variables and any database migration step. To change where a resource goes:
--region - clears the region. To change more, pipe edited JSON from hoist plan show PLAN_ID --json into hoist plan edit PLAN_ID. If the source changes, create a new plan. Set required values through variables.

Deploy

Deploy a folder in one step:
The CLI follows the deploy step by step until it is live or fails. --detach starts it and returns straight away. -m saves a note with the deploy. Or deploy a reviewed plan:
Keep the same request key if you retry the same deployment. Hoista rejects the key if the content changed. hoist deploys request REQUEST_UUID finds the deploy a key started.

Follow, cancel and roll back

In a terminal, hoist rollback without a deploy ID lets you pick one from the project’s deploys.
The deploy page for moodboard v4, live, with its checks and a Roll back to v3 buttonThe deploy page for moodboard v4, live, with its checks and a Roll back to v3 button

A finished deploy, with its checks and a button to roll back to v3.

A successful build does not prove the app works. Check the running project as well. Cancelling asks the provider to stop, and the provider may already be past that point. Rolling back switches which version serves traffic. It does not undo database migrations. If a request times out, check what happened before you retry. See operation outcomes. Providers lists the build types and actions each provider supports.

A failed deployment

Find where it failed and fix it.

Variables and domains

Set what the deploy needs.

Logs and metrics

Check the running app afterwards.