Skip to main content
Capsules give each branch its own copy of your app, created and updated by GitHub Actions. Use them to review changes before they reach your main environment.

​
Before you start

  • A project Monk has planned, with a MANIFEST. See Deploy an existing app.
  • The repository is on GitHub.
  • GitHub credentials, and cloud credentials if each branch gets its own cluster. Monk asks for both through forms.

​
Ask Monk

Choose where capsules run:
  • Own cluster per branch. Each branch gets a fresh cluster in the cloud and region you pick.
  • Shared cluster. Capsules run on a pool of nodes in an existing cluster.
You can leave out branches:

​
What you review

Credential forms open in the local dashboard. Then the plan shows the workflow file, where capsules run, their machine sizes and the secrets it will add to GitHub. The plan decides which services each capsule creates and which it shares. Production data is not copied. Nothing is created or pushed until you approve.

​
What you get

  • .github/workflows/dynenv.yml in your repository, built on monk-io/monk-actions
  • A scoped API key and the secrets the workflow needs, stored in a GitHub environment
  • An environment per branch, each with a preview URL
Capsules also appear in the web dashboard under Projects, Previews.

​
Control cost with a schedule

Each capsule costs money while it runs. Set a schedule so they are up only when people use them:
You can set a schedule for the whole project and change it for one capsule.

​
Secrets for capsules

Values go through the local dashboard, as for any secret.

​
Next