Application Settings

Name Application

Application Name is used to identify your application in the Bunnyshell interface.

Application Type

Depending on the Application Type, Bunnyshell adds frequently used Deploy Steps to your Application. Here is a complete list of supported Application Types:

Deploy type

  • Git -> Get Code from a Git Repository

  • Upload file -> Upload a file with your code

Git repository

An Application using Git as its Deploy Type needs to have a Git repository associated. Check the Git Repositories reference in order to connect your repositories:

What to deploy from repository (only for Git deploy type)

You can choose to deploy a Branch or Tag.

Deploy Path

The directory where your application will be deployed.

Application Domain

The Application Domain is used when you first create a One click Application to generate the web server virtual host.

Application user

Your Application user. After every deployment all your application files will be owned by this user. If the user does not exist it will be created. Usually this is your SFTP user.

Excluded files

If you have files in your git repository or in your archive, that you don't want to deploy on your server, you can add them here, separated by comma. Use relative paths to your application root directory. You can also use regexes and wildcards.

The default value is .git* which excludes all files that start with the .git prefix.

Shared folders

As described in the Application Deployment documentation, every application deployment represents a separate release folder with a separate code than the one currently live. However, if you want to share some folders between your application releases, you can add them in as separated comma list. Use relative paths to your application root directory.

Shared type

This field is related to the Shared folders fields and can have two possible values:

  • Link -> use this when you what to share a folder using symlinks between your releases. Let's presume you want to share the storage directory. On your first deployment, if the storage exists in your code, it will be copied in a separate shared_folders location. Every release with a symlink will point to this directory. In all subsequent deployments, if a storage directory exists in your archive or in your git, it will be removed and a symlink will be created to point to the storage directory in shared_folders. Note that you can also share files between deployments.

Using Shared Folders with Link Shared Type, means that every change you make to the shared directory in the PRE LINK Deploy steps is affecting the current live release. Use Link Shared Type only when you are not running commands at PRE LINK Deploy steps that affect the shared directory.

  • Copy -> Instead of using symlinks, this method copies the directory from the previous release when preparing the new one. This type of 'sharing folders' eliminates the issue stated above.

Don't use Copy Shared Type when your shared directory are big in size as you may consume all disk space. In this situation, consider using a shared disk or moving your data to an Object Storage.

Enable backup

Click to enable backups for your application. Check the Application Backups reference on how to restore these backups.