Add persistent app configuration UI #5

Open
opened 2026-07-29 12:25:21 +02:00 by daniels · 0 comments
Owner

Problem

Importarr is currently mostly env-configured. That is ops-friendly but less Arr-like for a new user who expects a Settings page.

Proposed change

Add a persisted non-secret configuration model and UI. Keep secrets env/file-based, but allow safe settings to be viewed and changed in the application.

Scope

  • SQLite-backed settings table or config snapshot.
  • Settings page for display name, SAB category, roots, bind/display options, and import behavior.
  • Read-only secret indicators for *_FILE / env-sourced secrets.
  • Config validation and restart-required indicators where needed.

Acceptance criteria

  • Non-secret settings can be viewed and updated from the UI/API.
  • Secret values are never returned by API or rendered in the UI.
  • The status page shows whether each setting comes from env/file/default/database.
## Problem Importarr is currently mostly env-configured. That is ops-friendly but less Arr-like for a new user who expects a Settings page. ## Proposed change Add a persisted non-secret configuration model and UI. Keep secrets env/file-based, but allow safe settings to be viewed and changed in the application. ## Scope - SQLite-backed settings table or config snapshot. - Settings page for display name, SAB category, roots, bind/display options, and import behavior. - Read-only secret indicators for `*_FILE` / env-sourced secrets. - Config validation and restart-required indicators where needed. ## Acceptance criteria - Non-secret settings can be viewed and updated from the UI/API. - Secret values are never returned by API or rendered in the UI. - The status page shows whether each setting comes from env/file/default/database.
daniels added the
prio
2
label 2026-07-29 14:12:17 +02:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: daniels/importarr#5