OpenClaw

## Install
 
Instantiate the module with:
 
    add-module ghcr.io/stell0/openclaw:latest 1
 
The output of the command will return the instance name.
Output example:
 
    {"module_id": "openclaw1", "image_name": "openclaw", "image_url": "ghcr.io/stell0/openclaw:latest"}
 
## Configure
 
Let's assume that the openclaw instance is named `openclaw1`.
 
Launch `configure-module`, by setting the following parameters:
- `<MODULE_PARAM1_NAME>`: <MODULE_PARAM1_DESCRIPTION>
- `<MODULE_PARAM2_NAME>`: <MODULE_PARAM2_DESCRIPTION>
- ...
 
Example:
 
    api-cli run module/openclaw1/configure-module --data '{}'
 
The above command will:
- start and configure the openclaw instance
- (describe configuration process)
- ...
 
The service is started with `--allow-unconfigured` so the gateway can come up
before the initial OpenClaw setup is completed.
 
Send a test HTTP request to the openclaw backend service:
 
    curl http://127.0.0.1/openclaw/
 
## Smarthost setting discovery
 
Some configuration settings, like the smarthost setup, are not part of the
`configure-module` action input: they are discovered by looking at some
Redis keys.  To ensure the module is always up-to-date with the
centralized [smarthost
setup](https://nethserver.github.io/ns8-core/core/smarthost/) every time
openclaw starts, the command `bin/discover-smarthost` runs and refreshes
the `state/smarthost.env` file with fresh values from Redis.
 
Furthermore if smarthost setup is changed when openclaw is already
running, the event handler `events/smarthost-changed/10reload_services`
restarts the main module service.
 
See also the `systemd/user/openclaw.service` file.
 
This setting discovery is just an example to understand how the module is
expected to work: it can be rewritten or discarded completely.
 
## Uninstall
 
To uninstall the instance: