CLI and migration

CLI and Migration

Core commands

Command	Purpose
jul serve	Run from a TOML configuration.
jul run	Start a zero-config static server or reverse proxy.
jul check	Validate and dry-run runtime construction.
jul lint	Validate and add best-practice findings.
jul fmt	Validate and produce canonical TOML.
jul healthcheck	Probe liveness or readiness.
jul version	Print version and build metadata.
jul completion	Generate shell completion.
jul import nginx	Translate supported NGINX configuration into Jul.IA TOML.

Use jul <command> --help and the README CLI section for current flags and exit codes.

CI pattern

A simple configuration gate is:

jul check -config server.toml
jul lint -strict -config server.toml
jul fmt -diff -config server.toml

Choose the exact policy for your repository; formatting does not preserve comments or original layout.

Migrating from NGINX

The importer is a best-effort starting point, not a promise of one-to-one compatibility.

jul import nginx -o server.toml /etc/nginx/nginx.conf
jul check -config server.toml

Recommended process:

1. Import the smallest meaningful configuration scope.
2. Review every reported unsupported directive and generated TODO.
3. Compare route matching, headers, TLS, body limits, and upstream behavior.
4. Add Jul.IA-native health, observability, and security settings.
5. Validate, test representative traffic, and cut over gradually.

The importer reports unmapped directives rather than silently discarding them. The current translation matrix and limitations live in the README migration section and migration example.

Compatibility

For config/API stability, deprecations, aliases, and versioning expectations, use the compatibility policy. Do not infer compatibility from a wiki example alone.