# Template for manual pull-only deploy (when not using CI-generated deploy.registry.env).
# CI workflow generates this file automatically; you normally only need secrets on disk.
#
# docker compose -f docker-compose.registry.yml --env-file deploy.registry.env up -d

# --- Registry boundary (swap when moving Gitea → Docker Hub) ---
# Gitea:  REGISTRY_PREFIX = <host>:<port>/<owner>
# Hub:    REGISTRY_PREFIX = docker.io/<user>   (or your username for implicit hub)
# Windows CI pushes via host.docker.internal:3000; browsers/Linux use wixur.ir:3000 (same Gitea).
REGISTRY_PREFIX=wixur.ir:3000/yourgiteauser

# Short git SHA from CI, or "latest" after a manual pull of :latest
IMAGE_TAG=latest

# Public HTTP port (router + Windows portproxy listen here) — 80 so users open http://wixur.ir
STAGING_HTTP_PORT=80
# Docker nginx bind on localhost only (must differ from 80 if portproxy owns 80)
STAGING_LOCAL_PORT=18088

# Absolute path on the server where database.staging.env and backend.staging.env live.
# Use forward slashes on Windows. Same path as Gitea Actions variable DEPLOY_SECRETS_DIR.
# DEPLOY_SECRETS_DIR=C:/dyolink/secrets
#
# Gitea Actions also needs CLONE_HOST=127.0.0.1:3000 when runner and Gitea share one Windows host.
# See STAGING-DEPLOY.md (do not use GITEA_* variable names — Gitea rejects them).