Skip to main content

Hot reload

Configuration changes apply without restarting the server, in two ways.

Reload config​

Reload config at the top of every Liberty Next editor page — or POST /admin/reload (superuser) — re-reads every configuration file and rebuilds the server's connectors, screens, menus, dashboards, charts, jobs and notification rules from them. If the new files fail to load, the previous configuration stays active and the error is shown.

Requests in progress finish with the configuration they started with; the next ones use the new one.

The file watcher​

With Hot reload on in Liberty Next → Administer → App — the default — the server watches its configuration files and reloads the part concerned a moment after a file changes (a save from Settings, an edit on the server, a git pull):

FileReloaded
menus.toml, screens.toml, charts.toml, dashboards.tomlThat part.
dictionary.tomlThe connectors' column information and the screens.
jobs.tomlThe jobs and their schedules.
notifications.tomlThe notification rules.
connectors.tomlThe connectors and their queries — not the pools.

Changes made within half a second are applied together.

Pools​

A pool change (address, password, size) is not applied by the watcher, so that a query in progress never loses its connection: after editing a pool, use Reload config.

Liberty Next → Administer → App​

Saving Liberty Next → Administer → App applies the licence, the AI assistant, OpenID Connect, the notifications and the UI defaults at once. The listening address, the port and the log level need a restart; so does the Oracle thick mode.

What needs a restart​

ChangeHow
Address, port, log level and Oracle thick mode in Liberty Next → Administer → App./liberty restart or liberty-ops restart.
An environment variable (.env, the service's environment file)A restart — ./liberty restart recreates nothing; for a changed .env, ./liberty start.
A plugin's Python codeA restart: modules are imported once.
A new release./liberty upgrade — see Upgrade and rollback.