Skip to content

Deployment Workflow

Step-by-Step

  1. Open the deploy page at /admin/config/development/drupalforge-deploy.
  2. Confirm backup destination and backup availability.
  3. Review the default Git reference and compatible remotes in Step 3.
  4. Choose a Git branch and backup to generate your deployment URL.
  5. Review the raw launch URL preview and editable payload preview.
  6. Use Deploy to launch current values in Drupal Forge.
  7. Use Save selection to persist payload edits for later visits and no-JS fallback.

Payload Behavior

  • Payload preview accepts multiline KEY=VALUE entries.
  • Comments and blank lines can be included during editing.
  • Duplicate keys follow last-value-wins behavior.
  • Launch link and payload preview are synchronized from the same values.

Auto-populated Variables

When metadata is available, deploy populates required variables including:

DP_REPO_BRANCH, DP_IMAGE, S3_BUCKET, S3_DATABASE_PATH, AWS_REGION, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, and ORIGIN_URL.

S3_DATABASE_PATH is composed as <s3_folder_prefix>/<backup_id> (or just <backup_id> when no prefix is configured), so nested backup prefixes are preserved in the generated payload without relying on backup source key/path metadata.

URL Contract Notes

  • Generated DrupalPod link uses comma-delimited hash entries (KEY=VALUE,KEY=VALUE).
  • Launch URL base must be HTTPS; non-HTTPS values fail closed.