deployment.md

Deployment

For information on how deployment works, see Vortex Deployment Documentation.

Hosting provider

This project is hosted on Acquia Cloud.

See Acquia hosting documentation for setup and configuration details.

Deployment workflow

1. Code is pushed to GitHub (source repository).
2. CI builds and tests the code.
3. On success, CI builds an artifact and pushes to Acquia Cloud (destination repository).
4. Acquia Cloud runs deployment hooks.

Branch naming on Acquia Cloud

• Feature branches (feature/ABC-123) → same name on Acquia
• Release tags (0.1.4) → deployment/0.1.4 branch on Acquia

Important rules

• No direct pushes to Acquia Cloud repository.
• Only Technical Lead and Deployer user should have access to Acquia repository.
• Technical Lead should regularly clean up feature/* and bugfix/* branches.

Hosting provider

This project is hosted on Lagoon.

See Lagoon hosting documentation for setup and configuration details.

Database refresh

To refresh the database in an existing Lagoon environment with production data:

VORTEX_DEPLOY_BRANCH=<YOUR/BRANCH-NAME> VORTEX_DEPLOY_ACTION=deploy_override_db ahoy deploy

Maintenance page

To serve a static maintenance page in place of the site, set the VORTEX_WEBSERVER_MAINTENANCE_MODE variable to 1 on the environment and redeploy it. The nginx container then answers every request with the page in .docker/config/nginx/maintenance.html. See Serve a maintenance page.

Project-specific configuration