Adding a new environment to a project
When adding a new environment to a project on Dropsolid Experience Platform, there are a few need to know's and manual actions required.
In the example below a new environment extraenv
is used
Following file will automatically be created by the platform, and should not be created manually
- settings.php file (see
etc/drupal/settings_extraenv.php
)
Following file needs to be created or altered so the env works correctly
- deploy script (see
bash/updates/update_extraenv.sh
)
Following files may need to exists or altered for your env to work correctly, depending on the structure and needs of the project
- additional_settings.php (see
etc/drupal/additional_settings.extraenv.php
) - htaccess file (see
etc/drupal/htaccess_extraenv
) - robots.txt file (see
etc/drupal/robots_extraenv.txt
)
Opinionated filenames in the install profiles
The installation profiles available in the Dropsolid Experience Cloud may have some default files that have an opinionated name.
An example is the etc/drupal/htaccess_live
file, used as default .htaccess file for the live environment of your project.
If the live environment of your project isn't named live
, you need to rename that file manually to have the expected default behaviour within the Dropsolid Experience Cloud.