Operate Native CEDAR

cedarcli is the normal control surface for a native installation. It prepares the correct profile for each command and delegates to CEDAR's process controller, which runs applications in the background and writes their logs below $CEDAR_HOME/log.

You should not need a separate terminal window for every microservice or frontend.

Start and Stop CEDAR

Start the complete native installation after its one-time configuration is finished:

cedarcli native start all

The aggregate starts infrastructure first, followed by the application processes. The matching stop command reverses that ownership safely:

cedarcli native stop all

During development, operate only the part you are changing:

cedarcli native start infra
cedarcli native start microservices
cedarcli native start frontends

cedarcli native stop frontends
cedarcli native stop microservices
cedarcli native stop infra

backends combines infrastructure and microservices. A single frontend or microservice can also be selected explicitly:

cedarcli native start backends
cedarcli native start frontend workspace
cedarcli native start microservice resource

The CLI refuses to stop a process merely because it occupies a familiar port. It first verifies that the process belongs to the expected CEDAR checkout.

See What Is Running

Use status for the broad view:

cedarcli native status

It reports microservices, infrastructure, and frontends in one grouped table. Managed application rows show PID, port/listener state, health, binary freshness, and cumulative log errors; infrastructure rows show their configured ports and availability. STALE means a healthy process is still running an older JAR. A ~ PID is a verified unmanaged CEDAR process that restart can adopt; ! is a foreign listener that native control will not touch. Use health when a script or test needs a simple success or failure result for the complete managed application tier:

cedarcli native health

For a continuously refreshed process view, run:

cedarcli native watch

Restart and Inspect Applications

After rebuilding a service, restart it by its process name:

cedarcli native restart resource

Follow its managed log with:

cedarcli native logs resource

The same commands work with frontend process names such as ui-workspace, ui-designer, and ui-openview.

Use the Profile Outside cedarcli

cedarcli loads the native profile for its own commands. A few standalone maintenance tools still depend on shell aliases and environment variables from that profile. Load it only in a shell where you intend to use those tools:

CEDAR_PROFILE=develop source "$CEDAR_HOME/cedar-development/bin/templates/cedar-profile-native.sh"

This is not required for routine cedarcli commands.

The cedarcli Manual covers repository work, build trains, hybrid and Docker modes, publication, and less frequently used command groups.