mirror of
https://github.com/koel/koel.git
synced 2026-04-26 09:15:59 +03:00
[GH-ISSUE #2050] [FR]: expand koel init to cover more configs #1081
Labels
No labels
Authentication
Dependencies
Documentation
Feature Request
Flac
Help Wanted
Installation/Setup
Integration
Mobile
PR Welcome
Pending Release
Performance
Playlist
S3
Search
Sync
[Pri] Low
[Pri] Normal
[Status] Keep Open
[Status] Needs Author Reply
[Status] Needs Review
[Status] Stale
[Status] Will Implement
[Type] Blessed
[Type] Bug
[Type] Duplicate
[Type] Enhancement
[Type] Help Request
[Type] Question
[Type] Task
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/koel-koel#1081
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @AEnterprise on GitHub (Aug 15, 2025).
Original GitHub issue: https://github.com/koel/koel/issues/2050
Originally assigned to: @phanan on GitHub.
Description
Current koel:init command only does setup for the database, but not other config options (like mail config, search providers, ...). Would be useful (especially since there is no good way to test/validate these right now) to have this ask about those
Additional information
Alternatively setting them from the ui with validation and test options could be useful.
i could probably make a pr later to add this to either if that's wanted
@phanan commented on GitHub (Aug 15, 2025):
I’d much prefer a CLI-based solution. We’ll also have to keep in mind that
the init command is runnable without user interactions.
On Fri, Aug 15, 2025 at 17:28 AEnterprise @.***> wrote:
@AEnterprise commented on GitHub (Aug 15, 2025):
it could have a flag you need to add for it to prompt these, i see it already does some stuff for detecting interactivity for not getting stuck in a database question loop, maybe it could only prompt for unset settings if ran interactively