#!/bin/sh
set -e

[ -f /run/secrets/postgres_p ] && export DB_PASSWORD="$(cat /run/secrets/postgres_p)"
[ -f /run/secrets/django_sk ] && export DJANGO_SECRET_KEY="$(cat /run/secrets/django_sk)"
[ -f /run/secrets/minio_rp ] && export AWS_S3_SECRET_ACCESS_KEY="$(cat /run/secrets/minio_rp)"
[ -f /run/secrets/minio_ru ] && export AWS_S3_ACCESS_KEY_ID="$(cat /run/secrets/minio_ru)"
[ -f /run/secrets/django_sp ] && export DJANGO_SUPERUSER_PASSWORD="$(cat /run/secrets/django_sp)"
[ -f /run/secrets/oidc_rpcs ] && export OIDC_RP_CLIENT_SECRET="$(cat /run/secrets/oidc_rpcs)"
[ -f /run/secrets/email_pass ] && export DJANGO_EMAIL_HOST_PASSWORD="$(cat /run/secrets/email_pass)"

# if not in "env" mode, then execute the original entrypoint and command
if [ ! "$1" = "-e" ]; then
  # Run WOPI configuration on startup if enabled (celery worker service only).
  # This ensures WOPI clients are configured immediately after each deploy,
  # rather than waiting for the next celery-beat cron tick (default: 3 AM).
  if [ "${RUN_WOPI_ON_STARTUP:-}" = "true" ]; then
    echo "🐳(entrypoint) running WOPI configuration on startup..."
    python manage.py trigger_wopi_configuration || echo "⚠ WOPI configuration failed (non-fatal, will retry on schedule)"
  fi
  exec "$@"
fi