forked from Nixius/authelia
1
0
Fork 0
ATLAS/docs
Leopere 4ac4de9df2
Path-based routing, tiered pricing, customer details, Stripe MCP
- Path-based routing: bc.a250.ca/login, /dashboard, /activate, etc.
- Tiered pricing: first 10 free (3mo), next 40 $20/yr->$100/mo, 51+ $200/mo
- Success page: instructs to check inbox for password + 2FA setup
- Messaging: LANDING_TAGLINE, LANDING_FEATURES env vars
- Domain validation: required, must resolve via DNS
- Customer details: phone required, sanitized email/phone, stored in LLDAP
- Stripe MCP: .cursor/mcp.json, stripe-setup.sh for products/prices
- Invoice webhook: migrate $20/yr subs to $100/mo on renewal

Made-with: Cursor
2026-03-04 17:05:42 -05:00
..
CI_CD_VAULT_SETUP.md Add ss-atlas service, config updates, ignore IDE cruft 2026-03-03 11:21:03 -05:00
OAUTH_SETUP.md Add ss-atlas service, config updates, ignore IDE cruft 2026-03-03 11:21:03 -05:00
README.md Deploy: prune old images after deploy, document full rebuild/redeploy 2026-03-03 11:35:07 -05:00
STRIPE_PAYMENT_LINK.md Path-based routing, tiered pricing, customer details, Stripe MCP 2026-03-04 17:05:42 -05:00
STRIPE_TIERED_PRICING.md Path-based routing, tiered pricing, customer details, Stripe MCP 2026-03-04 17:05:42 -05:00

README.md

Documentation Index

This directory contains comprehensive guides for Authelia deployment and configuration.

📚 Available Guides

🔧 Setup & Configuration

🚀 Getting Started

  1. Initial Deployment

    • Follow the main README.md for basic setup
    • Generate core secrets with ./generate-secrets.sh
    • Set up CI/CD vault using CI/CD Vault Setup
  2. OAuth Integration

    • Generate OAuth client secrets with ./scripts/generate-oauth-secrets.sh
    • Follow OAuth Setup Guide for service configuration
    • Configure individual services (Portainer, Gitea) with OAuth
  3. Production Deployment

    • Commit changes to trigger CI/CD pipeline
    • Monitor deployment through Woodpecker CI
    • Verify service health and authentication flows
  4. Full rebuild and redeploy (remove old stack/images)

    • Push to main (or run the production pipeline in Woodpecker). The pipeline: builds production images with --no-cache, pushes to registry, runs scripts/ci-deploy-production.sh (stack rm → wait → recreate secrets → deploy stack → health check → prune unused images).
    • No manual steps on the swarm manager; everything runs in CI.

🔑 Quick Reference

Essential Commands

# Generate core Authelia secrets (10 secrets)
./generate-secrets.sh

# Generate OAuth client secrets (2 additional secrets)  
./scripts/generate-oauth-secrets.sh

# Run development environment
docker compose -f docker-compose.dev.yml up -d

# Run tests
./tests/precommit.sh

Important URLs

Required Secrets (12 Total)

  • Core Secrets (5): LDAP, JWT, encryption, session, SMTP
  • OIDC Secrets (3): HMAC, private key, JWKS key
  • Client Secrets (4): Headscale (2), Portainer, Gitea

🔍 Troubleshooting

Common Issues

  • Service won't start: Check secrets in CI vault
  • OAuth fails: Verify redirect URIs and client secrets
  • Database errors: Check MariaDB connectivity and initialization
  • Health check fails: Verify Authelia startup and port binding

Useful Commands

# Check service logs
ssh macmini7 'docker service logs authelia_authelia --follow'

# Verify secrets access
ssh macmini7 'docker service logs authelia_authelia | grep -i secret'

# Test OAuth endpoints
curl -s https://login.a250.ca/.well-known/openid_configuration | jq .

📞 Support

For issues not covered in these guides:

  1. Check service logs for specific error messages
  2. Verify all secrets are present in CI vault
  3. Confirm network connectivity between services
  4. Review Authelia configuration for syntax errors

🔄 Updates

Keep documentation synchronized with code changes:

  • Update OAuth client configurations when adding new services
  • Refresh secret generation procedures when security requirements change
  • Document new troubleshooting steps as issues are resolved