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.
Configuration
Settings live in the database and are edited in the console. There is no configuration file.
Solidway does not read a configuration file. Settings are rows in the local database and are edited in System in the console; most take effect immediately, while listener and TLS changes apply on restart.
What is configurable
| Group | Settings |
|---|---|
| Network | Bind addresses, port, connection and first-byte timeouts |
| HTTPS | Domains (from the public access list), ACME challenge type, ports, HSTS, certificate state |
| Gateway | Cooldown durations for authentication failures, rate limits and unavailable upstreams; session affinity TTL |
| Selection | Strategy, per-credential weights, exploration rate |
| Usage | Collection on/off, per-request detail mode (off / errors / all), retention hours, sample rate |
| Alerts | Webhook URL, notify on recovery, minimum interval per provider |
| Auth | Session lifetime, cookie Secure flag |
| Access | Public base URLs clients use |
Things that are not settings
- Provider credentials are records, not settings: they are added per route, encrypted with the master key, and shown masked.
- Routes and API keys are records owned by a user.
- The master key comes from
<data_root>/master.key(or--master-keyfor recovery).
Where the values live
solidway.db in the data directory. Copying that file plus master.key to another
machine reproduces the configuration; nothing else on the host is read.