CFTunnels/portainer-automation/.env.example
hitanshu310 8f4af5e322 Hithomelabs/CFTunnels#99: Deploy portainer-automation service
- Add Dockerfile for portainer-automation (multi-stage build)
- Add standalone docker-compose.yaml for PA service
- Add application-prod.properties (prod Portainer :9443)
- Add application-ci.properties (CI test endpoints)
- Add .env.example with documented env vars for PA
- Add PORTAINER_STACK.md with deployment guide, env var tables, architecture diagram
- Add CI workflow (portainer_automation_build_push.yml) for image build/push
- Update root docker-compose.yaml to include PA service
2026-07-07 02:51:58 +05:30

39 lines
1.3 KiB
Plaintext

# ============================================
# Portainer Automation Service — Environment Variables
# ============================================
# Copy this file to .env and fill in your values.
# This service is NOT exposed via Cloudflare Tunnel (internal-only).
# --- Portainer Connection ---
# Portainer API Key for the target Portainer instance
# Create via Portainer UI: Settings → Authentication → Access tokens
# Dev: https://devdocker.hithomelabs.com → ptk_xxxx_dev_xxxx
# Prod: https://192.168.0.100:9443 → ptk_xxxx_prod_xxxx
PORTAINER_API_KEY=ptr_your_portainer_api_key_here
# Portainer endpoint ID (1 = primary Docker endpoint, 2 = remote)
PORTAINER_ENDPOINT_ID=2
# --- Service Auth ---
# API key that CI workflows send in the X-API-Key header
# to authenticate against this service's /api/deploy endpoint
PORTAINER_SERVICE_API_KEY=change-me
# --- Spring Profile ---
# Active Spring profile (local | ci | prod)
# local — uses devdocker.hithomelabs.com via Cloudflare Tunnel (default)
# ci — uses test/stub endpoints
# prod — uses production Portainer on internal network
SPRING_PROFILES_ACTIVE=local
# --- Deployment ---
# Deployment environment label (dev | test | prod)
ENV=dev
# Host port to map to container port 8081
HOST_PORT=8081