Skip to main content

Environments overview

Environments allow you to deploy different branches of your repository in isolated environments. They provide a safe space to test new features and changes before merging them into the main codebase and make it easier to collaborate with team members to ensure consistency across different stages of development.

In this section, we will cover how to create and manage environments in our platform, including how to deploy and configure them for different use cases.

Production environment​

The main difference between the production environment and preview environments is that the production environment is intended to be the live, public-facing version of your application or website, while preview environments are intended for testing changes or updates before they are deployed to the production environment. This allows you to test changes to your application or website without affecting the production environment or its users.

In Hubble Studio, the production environment is automatically assigned "production" domains, while preview environments can only have domains individually assigned to them.

Using the "Promote to Production" button you can change which environment is considered the production environment.

Manage environments​

Create environments​

  1. Navigate to the project you want to create a new environment for.
  2. Click on the "Create Environment" button.
  3. Enter a name for your environment in the "Name" field.
  4. Select a deployment strategy for your environment:
    • Manual: You can manually deploy changes to the environment using the "Create deployment" button in the environment dashboard.
    • Branch: The environment will automatically deploy whenever a new commit is pushed to a specific branch in the project's repository.
    • Tag: The environment will automatically deploy when a new tag is pushed to the project's repository.
  5. Depending on the deployment strategy you choose, you may need to configure additional settings, such as the branch name.
  6. Click on the "Create Environment" button to create your new environment.

That's it! You have now created a new environment for your project.

Modify existing environments​

  1. Log in to your account and navigate to the project where the environment is located.
  2. Click on the environment to open it, and then click on the "Settings" tab.
  3. In the settings, you can modify the environment name by editing the "Name" field.
  4. To change the deployment strategy, select one of these options:
    • Manual: You can manually deploy changes to the environment using the "Create deployment" button in the environment dashboard.
    • Branch: The environment will automatically deploy whenever a new commit is pushed to a specific branch in the project's repository.
    • Tag: The environment will automatically deploy when a new tag is pushed to the project's repository.
  5. After making the necessary changes, click on the "Save" button to save the modifications.

Deleting environments​

  1. Open the project of the environment that you want to delete.
  2. Click on the environment that you want to delete.
  3. Navigate to the "Settings" tab.
  4. Scroll down to the "Delete Environment" section.
  5. Click the "Delete" button.
  6. The environment will be deleted, and all associated resources will be removed.

Note: Deleting an environment will permanently remove all data associated with that environment, including deployments, logs, and any other associated resources. Be sure to export any important data before deleting an environment.

Use environments​

Environment variables​

Using environment variables allows you to configure your project’s build process and functionality based on different parameters and deploy contexts.

Learn more about the available options for environment variables, their overriding rules and constraints.

Access control​

You can customize how visitors access the environments of your project. Optimize visitor access for gated content, site administration, protected early access to your site for QA, and more.

hubble Studio offers these options for customizing visitor access:

  • Password Protection - Protect environments of your project with a password you control.

  • IP Allow List - Allows you to manage IP address that are allowed to visit your environments.