mirror of
https://github.com/koel/koel.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #472] a proper backend #332
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#332
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 @a7medo778 on GitHub (Oct 20, 2016).
Original GitHub issue: https://github.com/koel/koel/issues/472
hi there
first of all, wow this is amazing 👍
one of the most functional web-based music clients out there.
now to be blunt, i been on a mission to create a spotify like project for some time now, and while i understand that koel is a "personal" media server, why not make it a bit more
i am not saying recreate the wheel and start introducing new features, just check out https://github.com/ampache/ampache
radio, podcasts, discovery, top lists, transcoding...etc etc
its all there, if we can rely on ampache backend for features and koel for front end clients it would be the perfect combo
+
any hope for mobile clients maybe ? 🙏
@phanan commented on GitHub (Oct 22, 2016):
No, Koel doesn't aim to support the features Ampache does. The Ampache topic has been discussed several times before btw. In short, I intend to keep Koel simple and small.
Regarding mobile client: yes, I will do one when I have time.