Update site

Edited 2 years 8 months ago

To update a website, you must have permission to connect to the Cloud Platform environment using SSH.

https://docs.acquia.com/cloud-platform/manage/ssh/enable/add-key/

At the moment, updating a website must be done through a script that must be run in your local environment.

Script path:

./scripts/ci-deploy.sh

You can execute the script with the following syntax:

./scripts/ci-deploy.sh dev budweiserbr drupal

Where the declared arguments are:

1. environment

That can be:

  • dev
  • test
  • clone
  • live

2. site name

3. job

This script has 6 jobs:

1. drupal

It is responsible for performing database updates and importing configurations in drupal, respecting the ignore.
For those who know drupal, under the covers it will run a cym and an updb and a few more processes to ensure the consistency of ignore.

Example:

./scripts/ci-deploy.sh dev budweiserbr drupal

At the end of the process confirm the configuration import. Script does not run automatically, developer conference is required.

 

2. translate

It is responsible for checking and updating translations in Drupal, for example: if you define translations in the .po files of the abinbev_language module, this is responsible for registering these translations on the site.

Example:

./scripts/ci-deploy.sh dev budweiserbr translate

 

3. cohesion-config-import

It is responsible for importing only the cohesion components that had changes when a tag was raised in production.

Example:

./scripts/ci-deploy.sh dev budweiserbr cohesion-config-import

 

4. cohesion-config-sync-folder

It is responsible for ensuring the consistency of cohesion-config-import. As explained, partial import is nothing more than a comparison between the folder in the shared codebase, which is updated whenever a site is deployed, and the private folder of each site, so that a site stops generating these differences between one deploy and another it is necessary to update the private folder of each site. In case of any error, it is possible to run cohesion-config-import again, if it is executed successfully, it is necessary to run cohesion-config-sync-folder, so that the same differences are not pointed out.

Example:

./scripts/ci-deploy.sh dev budweiserbr cohesion-config-sync-folder

 

5. rebuild

It is responsible for rebuilding the cohesion components. It has a few more steps but at its core is dx8:rebuild.

Example:

./scripts/ci-deploy.sh dev budweiserbr rebuild

Note:  Commands should be executed in the order listed, unless you know what you are doing.

The last job is optional.

 

6. simple-sitemap-generate

It's responsible for generating or updating the site's sitemap, it's an optional command, since this process runs in cron, so it's not necessary to run it on deploy, only if you want to force an update ahead of cron.

Example:

./scripts/ci-deploy.sh dev budweiserbr simple-sitemap-generate