Search…
Bunnyshell use cases

Introduction

Let's look at some of the ways you can use Bunnyshell. We've listed only a handful below, so we encourage our users to come up with brand new ways of using our platform.
Whatever your experience, we'd love to hear how everything worked out for you.

Use Primary Environments, by creating some templates, then use them to create other environments:

You can do this either manually, via the UI, or programatically, via the CLI or using the Public API.
A good way to use this would be to have an Environment called "Template", which you can use as a fast-track to create identical-blueprint copies.

Use Ephemeral Environments, created automatically on Pull Requests.

Use them to test out or observe changes, then let them be automatically deleted when there's no need for them anymore (aka when the Pull Request is closed).
A good way to use this would be to have a single Environment creating ephemerals, although you may have multiple Primary Environments.
If you're already handling the build yourself, no worries: you can use the CLI to trigger an Environment creation & deployment (using the image you built) directly from your existing pipeline. Just add another stage.

Remote Development

Use it to sync your code into containers running in Kubernetes, and code directly in the cloud. No need for local tools. All you need locally is the code and your favourite IDE.

Automated testing, integrated in your testing pipeline

Use it to spin up new, isolated environments for end-to-end testing.
For example, you could use the CLI to create an Environment as a stage prior to running tests, then destroy the Environment after tests finished, as a final stage.
Copy link
On this page
Introduction
Use Primary Environments, by creating some templates, then use them to create other environments:
Use Ephemeral Environments, created automatically on Pull Requests.
Remote Development
Automated testing, integrated in your testing pipeline