# Gitea warm standby on the VPS - Phase 2. Pull-mirrors the home GitLab
# repo on a schedule (Gitea's built-in mirror feature - see
# manifests/setup-mirror-job.yaml for the one-time mirror setup), rather
# than a custom sync job.
#
# SQLite instead of the chart's default postgresql-ha + valkey-cluster:
# this is a single-instance standby holding one small mirrored repo, not
# a production multi-user Gitea - a full HA Postgres cluster + Valkey
# cluster would be a lot of extra moving parts (and VPS resources) for no
# real benefit here.
postgresql-ha:
  enabled: false
postgresql:
  enabled: false
valkey-cluster:
  enabled: false
valkey:
  enabled: false

persistence:
  enabled: true
  size: 10Gi
  storageClass: local-path

resources:
  requests:
    cpu: 50m
    memory: 128Mi
  limits:
    memory: 512Mi

gitea:
  admin:
    existingSecret: gitea-admin-secret
    passwordMode: keepUpdated

  config:
    database:
      DB_TYPE: sqlite3
    cache:
      ADAPTER: memory
    session:
      PROVIDER: memory
    queue:
      TYPE: level
    server:
      DOMAIN: gitea.kube.huskypup.net
      ROOT_URL: "https://gitea.kube.huskypup.net/"
      SSH_PORT: 22
      SSH_LISTEN_PORT: 2222
    mirror:
      ENABLED: true
      DEFAULT_INTERVAL: 6h

  metrics:
    enabled: false

# No ingress - reached over Netbird from home while it's up, or directly
# on the VPS during an actual promoted-standby incident (same pattern as
# the other vps-standby services).
service:
  http:
    type: ClusterIP
    port: 3000
  ssh:
    type: ClusterIP
    port: 22