Rename the default environment

You can set the name of your default/production environment when creating a project. To change it after project creation, follow the steps below. For consistency, the steps are all given using the CLI.

The examples below are based off of changing the default environment from old to main. Replace these names with what suits your situation.

If your site is already live, remember that deactivating an environment is a destructive operation that can result in data loss. To minimize potential issues, take the following steps:

  • Switch the default environment during non-peak hours.
  • Keep your data by taking a backup of the old environment
  • Reduce your DNS time-to-live (TTL) to a minimum.

Requirements 

If you have a domain set for your default environment, remove it before changing the default branch. Otherwise you get an error that default domain must be a valid project domain.

To change the default branch, you need to be an admin for the project

Note on source integrations 

The following steps depend of whether your project has a source integration.

If it doesn’t, Platform.sh is your primary remote repository for the project. If it does, GitHub, GitLab, or BitBucket hosts your primary remote repository for the project.

1. Create a main environment 

In your local copy of your repository, create a new environment from old called main:

platform environment:branch main old

In your local copy of the external repository, make sure your default branch is up to date:

git checkout old && git pull origin old

Then create the main branch off of your default branch and push it to the remote repository:

git checkout -b main
git push origin main

Source integrations include all branches, but don’t activate the corresponding environments in Platform.sh. Activate the main environment by running the following command:

platform environment:activate main

2. Copy settings 

If you have variables or other settings specific to your default environment, add those to the main environment.

For example, you may have variables for your production environment set to not be inheritable (such as if you set them with --inheritable=false through the CLI). These variables aren’t added automatically to child environments and so you need to add them to the main environment manually.

If you want the main environment to send emails, turn on outgoing email.

3. Make main a top-level branch 

To have main be your default, it needs to not be a child of old. Use the following command to remove its parent and make it a top-level branch:

platform environment:info -e main parent -

4. Make main the parent for other environments 

You probably have other environments that are children of old. For each environment, update its parent to main:

platform environment:info -e <ENVIRONMENT_NAME> parent main

To preserve your data on Platform.sh, it’s best to switch your work in progress to be based off of main.

Close any open pull/merge requests and resubmit them against main. If you want to continue working on branches after switching the default branch, rebase them by running git rebase --onto main <BRANCH_NAME>. Once you resubmit a request, it appears under the main environment on Platform.sh.

5. Deactivate the old branch 

To change your default branch, you first need to deactivate the existing default branch to remove protections. Deactivate the old environment without deleting it by running the following CLI command:

platform environment:delete --no-delete-branch old

6. Set main as the default branch 

Once old has been deactivated, set the project’s default branch to main:

platform project:info default_branch main

Once old has been deactivated, set the project’s default branch in Platform.sh to main:

platform project:info default_branch main

Follow the instructions to change the default branch to main for your provider:

7. Update DNS records 

Whether or not you’re using a CDN, if your site is live you have probably added a Platform.sh address somewhere when configuring a custom domain. If you have a CDN, it’s with the CDN provider. If you don’t have a CDN, it’s probably a CNAME record.

In either case, the setting probably has the old environment name as part of it. Update the setting to use the new environment name.

Verify that the new URL is correct by comparing it to the result from this command:

platform environment:info edge_hostname

8. Optional: Delete the old environment 

If you no longer want the old environment, such as to stop accidental use, delete it completely:

platform environment:delete --delete-branch old