Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Which services get a .env

Part of the configuration reference. A cross-cutting summary of which binaries ship a sample .env template, which ones layer .env/.env.$APP_ENV without shipping a sample, and which ones read no environment file at all.

Which services get a .env

mail_spooler, account_api, domain_sithbit, ipfs_daemon, ipfs_gateway, pop_server, imap_server, and smtp_server each ship a sample .env and .env.development in their crate directory — commented-out templates for every environment-variable override, using the precedence chain above. Copy the ones you need and uncomment.

The workspace’s other binaries deliberately don’t have one:

  • mail-grpc, sithbit-console, and sithbit-migrate use the same layered .env/.env.$APP_ENV mechanism as the binaries above (each reads them from the working directory, under its own MAIL_GRPC_* / SITHBIT_CONSOLE_* / SITHBIT_MIGRATE_* overrides), but ship no sample: each one’s whole surface is a single short table — mail_grpc/mail_grpc.example.toml already shows every gateway key, and the console’s and the migrator’s live above and in the migration chapter. The workspace-root .env that used to configure mail-grpc is retired — its legacy names (GRPC_SERVER_ADDRESS, DEFAULT_KEYPAIR, …) are no longer read by anything, and the file survives only as commented-out devnet fixture history.
  • The sithbit CLI (mail_client) reads no .env at all; its only configuration inputs are the config file sithbit config manages1 and the JSON_RPC_URL environment variable.
  • mail_program / alias_program / domain_program are on-chain SBF programs with no runtime environment.
  • appconfig_gen is a repo-side generator (cargo run -p appconfig-gen, never deployed): it reads iac/appconfig/’s AWS TOML documents and writes the Azure kvset artifact beside them, so it has no runtime configuration of its own.

Every remaining workspace crate is a library the binaries above link, with nothing to configure at runtime.

  1. This is the same file (~/.config/solana/cli/config.yml, same location on Windows too) the Solana CLI’s own solana config command reads and writes, if you already have it installed — see CLI Quickstart. ↩