ServerConfigurator
Configures Micronaut on behalf of an Elide application with default configuration state.
The developer may override these properties via their own configuration sources, which can be placed on the classpath as resources, loaded via Kubernetes configuration, or loaded via custom implementations of PropertySource / PropertySourcePropertyResolver.
On behalf of the developer, the following application components are configured:
Netty: Workers, native transports, threading, allocation, event loops
SSL: Modern suite of TLS ciphers and protocols
HTTP: HTTP/2, compression thresholds and modes, HTTP->HTTPS redirect
Access Log: Shows the HTTP access log via
stdout
during developmentDI Container: Eager initialization of Logic objects
No action is needed to enable the above components; the DI container loads and applies this configuration automatically at application startup.