# Example environment for the GitHub Actions registry-deploy workflow.
#
# Real values live in GitHub Actions secrets, NEVER in a committed file.
# This file documents the variable names and their shape so a human
# reading the repo can understand what the workflow needs without
# spelunking through .github/workflows/registry-deploy.yml.
#
# Set the real values via:
#   gh secret set OVH_SSH_HOST          --body "ovh.example.com"
#   gh secret set OVH_SSH_USER          --body "deploy-registry"
#   gh secret set OVH_SSH_PRIVATE_KEY   < ~/.ssh/registry_deploy
#
# See ops/registry/README.md "First-time OVH setup" for the full flow.

# OVH host the deploy SSHes into. Hostname or IPv4/IPv6 literal.
OVH_SSH_HOST=__OVH_HOST__

# Scoped deploy user on the OVH host. NOT root. The user is created
# during first-time setup with a sudoers rule that permits only
# `rsync` writes into /srv/registry/.
OVH_SSH_USER=deploy-registry

# Server-side paths the workflow rsyncs into. The container mounts
# /srv/registry read-only at runtime; only the host-side write path
# differs.
REGISTRY_DEPLOY_PATH=/srv/registry/r/
STORYBOOK_DEPLOY_PATH=/srv/registry/storybook/

# Snapshot directory for rollback. The workflow rsyncs the previous
# tree here before overwriting; rollback.sh promotes the most recent
# snapshot back to the live path.
SNAPSHOT_ROOT=/srv/registry/.previous/