• The first thing that will be shown is the service information:

• Busy space.

• Space consumed by existing test environments.

• Button for Add space if you don't have enough. You will access directly to modify the characteristics of hosting.

Do not confuse thetest environments(staging) with the test platform of cdmon.

Deploy a new test environment

If you do not have any active environment, you will see the button Deploy new test environment. Clicking will open a configuration window with the following steps:

1- Select the type of environment

• Full website: clone the entire folderwebwhere all the files of the web project or its CMS (WordPress, Prestashop, etc.) are.

• Existing project: clone an already created staging, a subdomain or multidomain of hosting.

• Custom environment: allows you to choose a specific folder from the server as the source of the staging.

2- Check the available space

The system will automatically calculate the estimated space needed for staging and compare it to the available hosting space:

• If there is enough space, the text will appear in green.

• If space is missing, it will be displayed in redand you can add more from the "Contract More Space" button or you will need to free up hosting space in order to create the Staging.

3- Select the database

If your website uses a database, you can select one to clone it next to the site.

The staging will duplicate the selected database, adding a random prefix to the original name to avoid conflicts.

4- Configure environment options

• PHP version: you can select a version equal or higher to that of main hosting.

• Private site (default marked option): Enables user-protected access for the test environment.

• Username and password: you can customize them or generate new ones with the available buttons.

• NOTE: This protection does not affect access to CMS administration (such as WordPress), only publicly visible content (frontend). It serves to prevent third parties from accessing the environment while testing or developments.

• Do not index content in search engines (default marked option): Prevents Google or other engines from indexing environment content and generating duplicate content.
  
  

All of these options can be modified later from the created environment.

5- The creation of the environment ends

• Click Next for Finish. In a few minutes, you will return to the list of test environments.

• You will return to the Test Environments panel created. You will see the new environment deployed with the following information:

• Subdomain assigned (example:stagingowts82cm.mystaging.es) with Active SSL.

• Associated folder.

• PHP version.

• Occupied space.

• Date of creation.

• Buttons Edit and Delete the environment.
  

From the list of environments:

• Click Edit test environment () to amend:

• PHP version.

• Privacy options and not index.
  
  

  

  
  

• If you want to delete a test environment, click Delete () to erase staging and free up space in your hosting.

How to visualize the test environment

Once the environment ofStaging, this will be housed in a random subdomain with active SSL such as: stagingowts82cm.mystaging.es

This subdomain already automatically points to the server IP so to view this URL directly from your browser.

Publish a test environment

Once you have already made the necessary changes, you can already replace the files currently published by those of a Staging you have created, in other words, the content of the Staging will be published in the main environment.

1. The tool will ask you to confirm whether or not you want."Activate maintenance mode" on the web to prevent data loss during the process. This is recommended when you have an online or similar store and you can record new data, keep in mind that when the Staging is published, this data will not be maintained. How to put your page into maintenance

1. The next step is to confirm where this Staging will be published. To replace the content of the test environment with the content of the main website, you can select "Full publication":

1. Below are the changes and differences detected in this Staging test environment compared to "base" content. You can check the files new/modified/deleted and the same for databases created:

1. Everyone's last step is confirmation of the occupied hosting space. The tool will display the "deemed necessary space" and also the available available", in which you need to have room to make this publication.
   
2. You can also activate the option of "Generate backup before publishing", which will keep a copy of the content currently published in case you want to download it or need to restore it later (you will need available space to store this backup)

1. The dashboard will show you that the Staging publishing process has begun and may take several minutes to complete, you will finally receive an email stating that the process is completed correctly.

Restore a rolback backup

If, by publishing a test environment, you marked the "Generate Backup Before Publishing", the system will automatically have created a copy of the content that was in production before publishing the Staging.

Once the process is complete, you will return to the dashboard with the list of test environments. In the environment you've published, a new button will appear in the actions column. This button will only be available if a backup was generated during publication:

When you access, a window will be displayed where you can consult the generated copy, with details such as the date, size occupied and the actions available:

1. Confirm restore in production:reverses the content of the main site to the state in which it was before publishing the staging.
2. Delete restoration point: Deletes the restore point to free up hosting space.

Note:Please note that these copies only include the items selected during publication. The rest of the hosting content will not be affected when restoring.

When you click on the green button, our dashboard will display a new confirmation window before proceeding:

You will receive an email from our system when the process is complete.

And you're done! The tool ofStagingallows you to work peacefully: you can test changes, update versions or test without affecting your website in production. In addition, an environment is generated fully functional, with up-to-date routes and free subdomain with SSL.