move optional config from app info page to deploy/settings page
Users couldn't find metadata provider fields (IGDB, ScreenScraper, etc.) on the app info page. Move them to the deploy page where all other settings (integrations, geo-restriction) already live. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
@@ -1,5 +1,12 @@
|
|||||||
## Changelog
|
## Changelog
|
||||||
|
|
||||||
|
### v0.32.8 — Move optional config to deploy/settings page (2026-02-27)
|
||||||
|
|
||||||
|
#### Changed
|
||||||
|
- **web/templates/deploy.html**: Optional config fields (metadata providers, API keys) now render on the deploy/settings page instead of the app info page — consistent with integrations and geo-restriction which already live there
|
||||||
|
- **web/handlers.go**: `deployHandler` now passes `OptionalConfig`, `CurrentValues`, `HasOptionalConfig` to the deploy template for deployed apps; `appDetailHandler` cleaned up to remove optional config data
|
||||||
|
- **web/templates/app_info.html**: Removed optional config section (HTML + JS) — no longer rendered here
|
||||||
|
|
||||||
### v0.32.7 — Fix FileBrowser config not being read on fresh deployments (2026-02-27)
|
### v0.32.7 — Fix FileBrowser config not being read on fresh deployments (2026-02-27)
|
||||||
|
|
||||||
#### Fixed
|
#### Fixed
|
||||||
|
|||||||
Reference in New Issue
Block a user