QuantLake
GitHub
Documentation

Configuration

Settings, where they are stored and how API keys are encrypted.

Settings live in ~/.config/quantlake/config.toml. Change them with quantlake config. The server picks up changes within a few seconds, so you don't need to restart it.

quantlake config list                       # all settings, with their defaults
quantlake config get server.concurrency
quantlake config set server.concurrency 8
quantlake config set server.min_free_gb 50
quantlake config unset server.min_free_gb   # back to the default
quantlake config path                       # where the file and the public key are

Settings

SettingDefaultDescription
server.concurrency4How many days to download at the same time (1–32)
server.min_free_gb20Stop starting new downloads when free disk space falls below this many GB
databento.max_monthly_usd0How much QuantLake may spend on paid Databento data each month, in US dollars. 0 means free data only. See Paying for Databento data
secrets.tardis_api_key–Your Tardis.dev API key (encrypted)
secrets.databento_api_key–Your Databento API key (encrypted)

Secrets

Set secrets from standard input, so that they don't end up in your shell history:

read -rs KEY && printf %s "$KEY" | quantlake config set secrets.tardis_api_key --stdin

Secrets are encrypted with the public key that install created, so the configuration file never contains them in plain text. Only the server can decrypt them, using the private key that systemd hands to it. QuantLake never prints a secret. It also refuses secrets passed as command-line arguments.