Operate

Use this section when a Librux runtime is already installed or about to be installed on a host.

Follow the pages in menu order when you are learning the operating model.

1. Runtime Configuration introduces the installed config.yaml, configurable runtime areas, and the surfaces used to change them.
2. CLI Tools covers the host from SSH, scripts, package lifecycle commands, and service diagnostics.
3. Web Console Manual introduces the browser operations surface for one host.
4. Time Sync Operations covers clock readiness, sync modes, and timing evidence.
5. Web and API Security explains browser login, API keys, and source-network gates before exposing the host beyond a trusted local environment.
6. Resource Control covers managed package admission, resource leases, and launcher-owned execution.
7. Deployment Checks closes the operating path with install, security, resource, time-sync, and cross-host readiness checks.
8. Product Frontend Modes explains how a product can keep Host Control APIs while replacing or disabling the bundled Web Console.

For daily operation, start from the Web Console when you have browser access and from the CLI when the host is only reachable over SSH, when automation is required, or when service-level diagnostics are needed. Use Runtime Configuration first when you need to understand why a host behaves differently from the default install.

Operator pages should stay command-oriented. They link to Reference when protocol fields or implementation details would interrupt the operating flow.