131868bdca
Major security, observability, and configuration improvements:
## Security Hardening
- Implemented configurable CORS (no more wildcards)
- Added comprehensive auth middleware for admin endpoints
- Enhanced webhook HMAC validation
- Added input validation and rate limiting
- Security headers and CSP policies
## Configuration Management
- Made N8N webhook URL configurable (WHOOSH_N8N_BASE_URL)
- Replaced all hardcoded endpoints with environment variables
- Added feature flags for LLM vs heuristic composition
- Gitea fetch hardening with EAGER_FILTER and FULL_RESCAN options
## API Completeness
- Implemented GetCouncilComposition function
- Added GET /api/v1/councils/{id} endpoint
- Council artifacts API (POST/GET /api/v1/councils/{id}/artifacts)
- /admin/health/details endpoint with component status
- Database lookup for repository URLs (no hardcoded fallbacks)
## Observability & Performance
- Added OpenTelemetry distributed tracing with goal/pulse correlation
- Performance optimization database indexes
- Comprehensive health monitoring
- Enhanced logging and error handling
## Infrastructure
- Production-ready P2P discovery (replaces mock implementation)
- Removed unused Redis configuration
- Enhanced Docker Swarm integration
- Added migration files for performance indexes
## Code Quality
- Comprehensive input validation
- Graceful error handling and failsafe fallbacks
- Backwards compatibility maintained
- Following security best practices
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
28 lines
1.5 KiB
Markdown
28 lines
1.5 KiB
Markdown
# render
|
|
|
|
|
|
[](https://goreportcard.com/report/github.com/go-chi/render)
|
|
[](https://pkg.go.dev/github.com/go-chi/render)
|
|
|
|
The `render` package helps manage HTTP request / response payloads.
|
|
|
|
Every well-designed, robust and maintainable Web Service / REST API also needs
|
|
well-*defined* request and response payloads. Together with the endpoint handlers,
|
|
the request and response payloads make up the contract between your server and the
|
|
clients calling on it.
|
|
|
|
Typically in a REST API application, you will have your data models (objects/structs)
|
|
that hold lower-level runtime application state, and at times you need to assemble,
|
|
decorate, hide or transform the representation before responding to a client. That
|
|
server output (response payload) structure, is also likely the input structure to
|
|
another handler on the server.
|
|
|
|
This is where `render` comes in - offering a few simple helpers and interfaces to
|
|
provide a simple pattern for managing payload encoding and decoding.
|
|
|
|
We've also combined it with some helpers for responding to content types and parsing
|
|
request bodies. Please have a look at the [rest](https://github.com/go-chi/chi/blob/master/_examples/rest/main.go)
|
|
example which uses the latest chi/render sub-pkg.
|
|
|
|
All feedback is welcome, thank you!
|