Solidway v0.1.0 is released under AGPL-3.0; source and releases are on GitHub. This documentation is being rewritten against the release — pages outside Quick start and Reference still describe planned behaviour. The current reference lives in docs/getting-started.md and docs/architecture.md in the repository.

Logs

Where the gateway writes, how to read it, and what is never written.

Where logs go

Installation	Destination
Linux package	stderr → `journalctl -u solidway`
Binary	stderr of the process
Desktop app	`<data_root>/solidway.log` (also the place startup failures are explained)

What they look like

Text lines with a timestamp, level and structured fields (key=value), for example:

2026-10-27T12:41:03.512Z  INFO solidway_api: frontend assets resolved source="embedded"
2026-10-27T12:41:03.540Z  WARN solidway_api::crypto: master key file created path=/var/lib/solidway/master.key

Set the level with the RUST_LOG environment variable (for example RUST_LOG=info,solidway_core=debug).

Startup events

Besides logs, the binary writes a small set of machine-readable lines to stdout — listener address, bootstrap URL, desktop login URL, bind failures. They are consumed by the desktop app and are documented under CLI.

What is never logged

Bootstrap tokens and desktop login tokens are printed once to stdout and never written to solidway.log. Provider credentials appear only masked. Request and response bodies are not logged.

Not implemented

There is no JSON log format switch and no OpenTelemetry trace export.