Project Settings

Introduction

To access the Project Settings page:

1. Click on the project name in the upper-right corner of the Bunnyshell interface.

2. Select View all projects.

3. Click the Settings button of the desired page. Here you are able to edit the Project features listed below.

General Settings

Here you can modify the name of your current project. Simply type the new name, then click Save changes.

Bunnyshell notifies you if the name is already used by a separate project. In this case, you can Save changes only after choosing a different name.

Build Settings

In the Build Settings screen you can edit various aspects related to the image builder, including:

• The infrastructure on which the builder should run

• The build cluster

• Allocated resources

• Registries where application images should be stored.

Read more about this on the Build Settings documentation page linked below.

https://documentation.bunnyshell.com/using-bunnyshell/build-settingsdocumentation.bunnyshell.com

Project Variables

This screen is where you can Add, Edit and Delete Project Variables. In Bunnyshell, Project variables are:

• Automatically inherited in all new environments from a specific project

• Available at runtime, as well as during builds and deploys.

Read more about this on the Project Variables documentation page linked below.

https://documentation.bunnyshell.com/using-bunnyshell/variables/project-variablesdocumentation.bunnyshell.com

Environment Rules

Rules set up at the Project level will be automatically inherited by all new Environments and will allow you to configure the lifecycle of your Environments.

Auto-update

Thanks to this feature, you can keep your primary up to date when changes are merged in your main Git branch.

https://documentation.bunnyshell.com/quick-guides/automatically-updating-your-environment-with-new-commits-mergesdocumentation.bunnyshell.com

Environment availability

Environment availability rules are an easy way to control the costs of all your primary and ephemeral environments. Such rules allow you to define the timeframes in which these environments will run.

https://documentation.bunnyshell.com/quick-guides/setting-up-environment-availability-rulesdocumentation.bunnyshell.com