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.

Configuration

The bootstrap file — four settings, and nothing else.

The configuration file exists to start the process. It answers four questions and nothing more. Providers, credentials, routes, routing policy and alerts are managed in the console.

The whole file

[server]
listen = "0.0.0.0:8080"
public_url = "https://gateway.example.com"

[console]
listen = "127.0.0.1:8081"

[state]
path = "/var/lib/solidway"

[telemetry]
# optional; see Metrics and Logs

server

Key	Type	Notes
`listen`	string	Address and port the gateway accepts traffic on
`public_url`	string	The domain clients use. Absolute URLs are built from it, and the `Host` header is validated against it.

public_url matters for more than bookkeeping: it is what the gateway considers itself to be, so a request arriving with an unexpected Host can be rejected before it is routed.

console

Key	Type	Notes
`listen`	string	Where the management console is served

Bind this to a private interface. The console is an administrative surface; it does not need to be reachable from the internet.

state

Key	Type	Notes
`path`	string	Directory holding console-managed configuration

This directory is the source of truth for routing. It is read at startup and written on change. Back it up, and put it on persistent storage in a container environment.

telemetry

Optional exporter settings. These are infrastructure endpoints, which is why they live in the bootstrap file rather than in the console. See Metrics and Logs.

What is not here

There is deliberately no providers, routes or alerts section. If you are looking for where to add a provider, that is the console:

Loading

The file is read once at startup and cannot be changed at runtime. Changing the listen address or the public domain is a restart; changing anything about traffic is a console action and takes effect immediately.