Settings UI: move tunables from config to a DB-backed settings page #1

Closed
opened 2026-06-21 16:21:06 +00:00 by Kessinen · 0 comments
Owner

Now that there is a web UI, several config values could be edited live in the browser and persisted to SQLite (alongside logs.db) instead of a config-file edit + restart.

Candidates to expose:

  • Encoding profiles: crf / preset per media type (dvd/bluray/webdl/tvrip)
  • encoding.lp thread cap (knob landed in #5; this issue tracks its UI surfacing)
  • omdb_api_key (secret field)
  • log_retention_days
  • delete-originals (-d) as a toggle

Stays in config (bootstrap): paths.*, http_addr.

Implies a settings table, a settings API (GET/PUT), config becomes seed/defaults with DB overriding. Mutations pull in the auth issue (#2).

Now that there is a web UI, several config values could be edited live in the browser and persisted to SQLite (alongside logs.db) instead of a config-file edit + restart. Candidates to expose: - Encoding profiles: crf / preset per media type (dvd/bluray/webdl/tvrip) - encoding.lp thread cap (knob landed in #5; this issue tracks its UI surfacing) - omdb_api_key (secret field) - log_retention_days - delete-originals (-d) as a toggle Stays in config (bootstrap): paths.*, http_addr. Implies a settings table, a settings API (GET/PUT), config becomes seed/defaults with DB overriding. Mutations pull in the auth issue (#2).
Kessinen added the enhancementui labels 2026-06-21 16:21:06 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Kessinen/av1dae#1