commandbox-embedded-server

Start the embedded Undertow server directly from your BoxLang project root directory to launch with sensible defaults and automatic port selection. This eliminates manual setup by applying configuration from your server.json file directly to the local server context.

Configure JVM arguments and SSL/TLS by defining web settings, bindings, and environment profiles within your server.json file. This approach supports both development and production contexts while ensuring safe defaults and isolated server contexts for your BoxLang application.

Yes, you can manage multi-site hosting by configuring alias mappings and bindings within your server.json file. This allows the embedded Undertow server to route multiple sites across distinct development and production profiles from a single project configuration.

The best way to apply URL rewrites and basic auth is by defining security rules and web settings inside your server.json file. This automates the configuration of the embedded Undertow server, simplifying local development and testing workflows safely.

No, managing an embedded server does not require manual process handling because the Skill automates the complete server lifecycle. It handles starting, stopping, and restarting the Undertow server directly while applying isolated server contexts and safe defaults.

Using server.json profiles separates development and production environment configurations for your BoxLang apps. This ensures distinct JVM arguments, SSL/TLS bindings, and web settings apply safely per environment without ad-hoc server runs or manual overrides.