These pages describe the intended behaviour of the gateway. The open-source release and the enterprise edition are being split out; details will be updated when the first release ships.
CLI
The few commands the binary accepts. Everything else is in the console.
The command line is small on purpose. It starts the process and reports on it; it does not configure anything.
Commands
| Command | Purpose |
|---|---|
solidway run |
Start the gateway |
solidway check |
Validate the bootstrap file and exit |
solidway health |
Query a running instance |
solidway version |
Print version and build target |
There is no command for listing routes or providers, because those live in the console and change without a restart.
Flags
| Flag | Applies to | Notes |
|---|---|---|
--config <path> |
all | Defaults to /etc/solidway/solidway.toml |
--log-format <json|text> |
run |
text is for reading in a terminal |
--log-level <level> |
run |
error, warn, info, debug, trace |
Checking the bootstrap file
solidway check --config ./solidway.tomlExits non-zero and prints the failing key path when the file is invalid. Run it in CI against the file you intend to deploy.
Exit codes
| Code | Meaning |
|---|---|
0 |
Success |
1 |
Configuration invalid |
2 |
Usage error |
3 |
The state directory is missing or not writable |
Signals
| Signal | Effect |
|---|---|
SIGTERM |
Stop accepting connections, drain in-flight requests, exit |
SIGHUP |
Re-read the bootstrap file |
Changing routing does not need a signal. It is a console action.