Multi-Tenant Config-System: Ein furt für viele Websites #89
Labels
No labels
apache
api
api-contract
api-gateway
authentication
automation
breaking-change
comments
component/deployment
component/documentation
component/service-management
configuration
contact-form
coordination/cross-repo
coordination/needed
core
deployment
development
development-ready
digital-sovereignty
distribution
effort
large
effort
medium
effort
small
enhancement
frontend
furt-service
furt/gateway
furt/installation
gateway
gateway-integration
generator
gitea-testing
health-check
help-wanted
hugo
hugo-integration
infrastructure
installation
logging
low-tech
mail
meta
meta/duplicate
meta/planning
meta/wontfix
monitoring
observability
openapi
organization
packaging
performance
planning
platform/linux
priority
high
priority
low
priority
medium
production
question
sagjan
security
service
service-analytics
service-development
service-formular2mail
service-newsletter
service-request
service-sagjan
session
blocker
session
handover
session
next
shortcode
specs
ssl
status
blocked
status
done
status
in-progress
status
review
status
to-go
systemd
testing
tooling
type
admin
type
bug
type
config
type
deployment
type
docs
type
enhancement
type
feature
type
handover
type
infrastructure
type
installation
type
maintenance
type
migration
type/refactor
type
research
type
security
type/testing
v0.1.0
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: DAW/furt#89
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
Ein Server, eine furt-Instanz, aber 5 verschiedene Websites mit:
Solution
nginx-style Config mit API-Key-based Mail-Routing
Testing Required
Abhängig von: Issue #71 (Research)
Multi-Tenant System Complete
Das Multi-Tenant-System ist vollständig implementiert und getestet:
Implementierte Features
furt.confParserrate_limit_api_key_max,rate_limit_ip_max,rate_limit_windowcors_allowed_originsmit Environment-FallbackConfig-Integration komplett
Alle Parameter aus
furt.conf.examplewerden jetzt tatsächlich verwendet:[server]Section: host, port, timeouts, CORS, logging[security]Section: Rate-Limits, Test-Endpoint-Steuerung[smtp_default]Section: Standard-SMTP für alle API-Keys[api_key "name"]Sections: Pro-Tenant Konfiguration mit Custom-SMTPFunktionale Tests bestanden
Status: COMPLETE ✅
Nächster Schritt: Installation.md Reality-Check für saubere Produktiv-Installation (#91)