Skip to content
abcnorio docs

Orchestrator

Orchestrator

Section titled “Orchestrator”

Purpose

Section titled “Purpose”

The orchestrator is the control plane for frontend deploy and data-sync operations.

  • Runs production/preview build and restore workflows.
  • Syncs frontend code to staging from the canonical staging branch.
  • Runs dev/staging media copy and backup operations.
  • Exposes status consumed by the WordPress deployment dashboard.

Code to staging

Section titled “Code to staging”

Staging deploys are branch-based.

  • Source of truth: abcnorio-astro/site-dev in the staging branch.
  • Push action exports branch head commit into site-staging.
  • Then installs dependencies and clears the Vite cache.
  • On complete, status reports the head commit SHA (for logs).

There is no tag approval/versioning step in this flow.

Build Backups

Section titled “Build Backups”

Build archives are written to build-archives/static-backup. Retention is enforced by orchestrator cleanup settings (MAX_BACKUPS).

Media copying and backups

Section titled “Media copying and backups”

Media archives are written to build-archives/media. Retention is enforced by MAX_MEDIA_BACKUPS.