After you have a codebase provisioned by Acquia, you can create your sites by using the codebase and view the existing sites. The number of sites visible to you is based on your individual permission within the Multi-Experience Operations entitlement.
The system displays all available codebases along with the number of sites and environments associated with the codebases.
Select a codebase to view its associated sites.
Click Sites.
The system displays all the sites created through the codebase.
You can view the following information about your sites:
Name of the site
Description about the site
Number of site instances for the site. For example, if a site is deployed to dev, stage, and prod, the site has 3 site instances and the Cloud Platform user interface displays the message: Deployed on 3 environments.
Creating a site
Important
The number of sites that you can create from a codebase depends on the terms and conditions of your Multi-Experience Operations entitlement.
The system displays all available codebases along with the number of sites and environments associated with the codebases.
Select a codebase to view its associated sites.
Click Sites.
Click Create Site.
The system displays the Create Site page.
In Site name, specify the name through which you want to identify the site. This name must consist of 1-50 alphanumeric characters (a-z, A-Z, 0-9) with no special characters.
In Technical domain name, enter a name for the site. After you set this value, you cannot update it later.
Note
The codebase and names are reserved. Do not use these names as technical domain names for any site.
Associating sites with environments
After you create a site, you must associate it with one or more environments to create site instances. Site instances are essential for you to use the site. The system creates databases and associates domains with the site after you create site instances. You can associate sites with environments that use the same codebase. In addition, you can associate environments with sites. For more information, visit Managing Environments.
The system displays all available codebases along with the number of sites and environments associated with the codebases.
Select a codebase to view its associated sites.
Click Sites.
Select the site that you want to associate with environments.
The system displays the Site Overview page.
Click Associate environment.
The system displays the Associate Site with Environments page and lists all the environments associated with the codebase.
Select environments.
Click Associate Environments.
The system associates the site with the selected environments and creates site instances. Cloud Platform might take some time to associate the site with environments. Until the association is complete, the status is displayed as Pending.
Site Overview page
The Site Overview page has the following fields and action items:
Field
Description
Description
Displays the description for the site. The system displays this field only if you have added a description for the site through Actions > Add description.
Codebase
Displays the codebase that is used to create the site.
Actions > Add description or Edit description
Enables you to add a new description or update an existing description for the site.
Actions > Rename site
Enables you to rename the site.
Copying database and files
To copy database and files from one environment to another:
The system displays all available codebases along with the number of sites and environments associated with the codebases.
Select a codebase to view its associated sites.
Click Sites.
Select the site that you want to dissociate from the environment.
In the Associated Environments section, locate the specific environment.
Go to Actions > Dissociate.
Enter CONFIRM and click Dissociate.
This removes the association of the environment from the site.
Monitoring Deployments
In an active at-scale deployment, individual sites use different code versions as the rollout progresses through batches.
Code Version: The Sites page displays the current gitRef for each site instance.
Maintenance State: If you configure site-level Cloud Hooks to enter and exit maintenance mode, a site enters maintenance mode only in its specific update window. After the update completes, the site exits maintenance mode and points to the new code version, even if other sites in the environment await updates.
Managing Sites
Accessing sites
After you have a codebase provisioned by Acquia, you can create your sites by using the codebase and view the existing sites. The number of sites visible to you is based on your individual permission within the Multi-Experience Operations entitlement.
The system displays all available codebases along with the number of sites and environments associated with the codebases.
Select a codebase to view its associated sites.
Click Sites.
The system displays all the sites created through the codebase.
You can view the following information about your sites:
Name of the site
Description about the site
Number of site instances for the site. For example, if a site is deployed to dev, stage, and prod, the site has 3 site instances and the Cloud Platform user interface displays the message: Deployed on 3 environments.
Creating a site
Important
The number of sites that you can create from a codebase depends on the terms and conditions of your Multi-Experience Operations entitlement.
The system displays all available codebases along with the number of sites and environments associated with the codebases.
Select a codebase to view its associated sites.
Click Sites.
Click Create Site.
The system displays the Create Site page.
In Site name, specify the name through which you want to identify the site. This name must consist of 1-50 alphanumeric characters (a-z, A-Z, 0-9) with no special characters.
In Technical domain name, enter a name for the site. After you set this value, you cannot update it later.
Note
The codebase and names are reserved. Do not use these names as technical domain names for any site.
Associating sites with environments
After you create a site, you must associate it with one or more environments to create site instances. Site instances are essential for you to use the site. The system creates databases and associates domains with the site after you create site instances. You can associate sites with environments that use the same codebase. In addition, you can associate environments with sites. For more information, visit Managing Environments.
The system displays all available codebases along with the number of sites and environments associated with the codebases.
Select a codebase to view its associated sites.
Click Sites.
Select the site that you want to associate with environments.
The system displays the Site Overview page.
Click Associate environment.
The system displays the Associate Site with Environments page and lists all the environments associated with the codebase.
Select environments.
Click Associate Environments.
The system associates the site with the selected environments and creates site instances. Cloud Platform might take some time to associate the site with environments. Until the association is complete, the status is displayed as Pending.
Site Overview page
The Site Overview page has the following fields and action items:
Field
Description
Description
Displays the description for the site. The system displays this field only if you have added a description for the site through Actions > Add description.
Codebase
Displays the codebase that is used to create the site.
Actions > Add description or Edit description
Enables you to add a new description or update an existing description for the site.
Actions > Rename site
Enables you to rename the site.
Copying database and files
To copy database and files from one environment to another:
The system displays all available codebases along with the number of sites and environments associated with the codebases.
Select a codebase to view its associated sites.
Click Sites.
Select the site that you want to dissociate from the environment.
In the Associated Environments section, locate the specific environment.
Go to Actions > Dissociate.
Enter CONFIRM and click Dissociate.
This removes the association of the environment from the site.
Monitoring Deployments
In an active at-scale deployment, individual sites use different code versions as the rollout progresses through batches.
Code Version: The Sites page displays the current gitRef for each site instance.
Maintenance State: If you configure site-level Cloud Hooks to enter and exit maintenance mode, a site enters maintenance mode only in its specific update window. After the update completes, the site exits maintenance mode and points to the new code version, even if other sites in the environment await updates.
default
In Description, enter a description for the site
Click Create Site.
The system creates the site.
Note
You cannot create environments. To get a new environment provisioned, contact Acquia Support.
You cannot copy database to an environment where the Protection mode is enabled. For more information, visit Using the Protection mode.
In the Data to copy section, select the Database and/or Files.
Click Copy.
This copies the selected database and/or files from one environment to another.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
default
In Description, enter a description for the site
Click Create Site.
The system creates the site.
Note
You cannot create environments. To get a new environment provisioned, contact Acquia Support.
You cannot copy database to an environment where the Protection mode is enabled. For more information, visit Using the Protection mode.
In the Data to copy section, select the Database and/or Files.
Click Copy.
This copies the selected database and/or files from one environment to another.
Did not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Multi-Experience Operations