2025-11-29 12:17:01 +01:00
|
|
|
[server]
|
|
|
|
|
host = "0.0.0.0"
|
|
|
|
|
port = 8080
|
|
|
|
|
# Uncomment for production with HTTPS:
|
|
|
|
|
# public_base_url = "https://idp.example.com"
|
|
|
|
|
|
|
|
|
|
[database]
|
refactor: update crabidp references to barycenter and add Gateway API support
Replace all remaining references to "crabidp" with "barycenter" across:
- Source code (error diagnostics, CLI name, comments)
- Configuration files and defaults
- Environment variable prefixes (CRABIDP__ → BARYCENTER__)
- Documentation (CLAUDE.md, README.md, DEPLOYMENT.md)
- Deployment configurations (Docker Compose, Helm, systemd, FreeBSD, illumos)
- Database filenames (crabidp.db → barycenter.db)
Add Kubernetes Gateway API support to Helm chart:
- New HTTPRoute template for Gateway API
- Configurable parentRefs, hostnames, filters, and weights
- Support for advanced traffic management features
- Gateway API as modern alternative to traditional Ingress
- Documentation and examples in DEPLOYMENT.md
Benefits of Gateway API:
- More expressive and extensible routing
- Role-oriented design with separation of concerns
- Better vendor portability
- Advanced traffic management capabilities
The Helm chart now supports both traditional Ingress and
Gateway API, allowing users to choose based on their cluster
capabilities and requirements.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
2025-11-29 15:38:07 +01:00
|
|
|
url = "sqlite://barycenter.db?mode=rwc"
|
2025-11-29 12:17:01 +01:00
|
|
|
|
|
|
|
|
[keys]
|
|
|
|
|
jwks_path = "data/jwks.json"
|
|
|
|
|
private_key_path = "data/private_key.pem"
|
|
|
|
|
alg = "RS256"
|
|
|
|
|
|
|
|
|
|
[federation]
|
|
|
|
|
trust_anchors = []
|