Manage your application
- Dashboard
- Inspect HTTP traffic, package CPU and memory, network traffic, and workspace storage. See Dashboard metrics.
- Deploy
- Find Git connection details, inspect package status, and start or stop compiled packages. Use Redeploy to compile the latest pushed source without a new push.
- Logs
- Read application output, build events, and HTTP events. See Logs for collection behavior and search examples.
- Traces
- Find slow or failing operations and inspect their spans. Start with tracing setup, then explore traces.
- Config
- Inspect the parsed configuration. This view is read-only. Edit leilani.json locally, commit it, and push to change package arguments, HTTP routing, or access-control rules.
Deploy shows each package’s confirmed state: awaiting-deployment, stopped, restarting, building, running, or failed. Running means a process has started; it is not an HTTP health check. Console pages remain accessible before deployment.
Stop sends SIGTERM and allows up to 30 seconds before terminating remaining processes. It cancels automatic retries for that package. Stopping every package keeps the VM available for Terminal. Start reuses the compiled executable and resets that package’s retry budget; commit and push source or leilani.json changes, or use Redeploy after changing console environment variables.
During compilation, an existing deployment continues running. A build failure leaves it in place. After a successful build, Leilani stops the old VM and starts the replacement, causing downtime. If replacement startup fails, the workspace stays offline; there is no automatic rollback. Read Logs to identify the cause. If you change source or leilani.json locally, commit and push the fix. If you change a variable in Environment, use Redeploy to rebuild the pushed source with that value. Redeploy does not upload local files. Closing the build-output dialog does not cancel an accepted deployment.