Configuration

Japella is configured primarily via config.yaml (typically mounted at /config/config.yaml in containers, or ~/.config/japella/config.yaml). Environment variables override matching values after the file is loaded.

Environment variables

  • JAPELLA_DB_HOST

  • JAPELLA_DB_PORT

  • JAPELLA_DB_NAME

  • JAPELLA_DB_USER

  • JAPELLA_DB_PASS

  • JAPELLA_SECURE_COOKIES

  • JAPELLA_DEBUG

  • JAPELLA_LOG_LEVEL

  • JAPELLA_TLS_CRT_PATH

  • JAPELLA_TLS_KEY_PATH

  • JAPELLA_LISTEN_ADDRESS

Log level (logLevel)

Set the logrus log level with the top-level logLevel key. Accepted values (case-insensitive): panic, fatal, error, warn / warning, info, debug, trace. Default is info when unset.

config.yaml
configVersion: 2
logLevel: DEBUG

Precedence:

  1. JAPELLA_DEBUG=true forces debug (legacy convenience flag).

  2. Otherwise JAPELLA_LOG_LEVEL overrides logLevel from the file when set.

  3. Otherwise logLevel from config.yaml.

  4. Otherwise info.

Subsystem debug logging (Settings)

Fine-grained debug logging is controlled from the web UI under Settings → Debug, not from logLevel. Toggle checkboxes such as Auth debug logging, Feed fetcher debug logging, and HTTP client debug logging. Changes apply immediately without restarting the service.

These flags are independent of logLevel: leave logLevel at info and enable only the subsystem you need. Global logLevel: debug still enables ordinary log.Debugf calls everywhere.

Further configuration