mirror of
https://github.com/koel/koel.git
synced 2026-04-25 16:56:02 +03:00
[GH-ISSUE #1929] Koel Plus user can't connect s3, at least does not sync #1036
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#1036
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 @iDomas on GitHub (May 22, 2025).
Original GitHub issue: https://github.com/koel/koel/issues/1929
Since you’re not using a cloud storage, there’s no need to set a media path.This is the message I get after I try to go to Settings after I successfully connected connected to AWS S3.
My environment is docker compose on dokploy.
Also noticed that for docker compose some environment variables are not taken for example OUTPUT_BIT_RATE,
I set to 320, and after
php artesian koel:initin .env file it stays 128@phanan commented on GitHub (May 27, 2025):
Indeed, the message should say "since you ARE using a cloud storage…" However, what do you mean by "at least doesn't sync"?
@iDomas commented on GitHub (May 27, 2025):
by "at least doesn't sync" I mean that it does not pick up from cloud storage tracks which I uploaded directly
@phanan commented on GitHub (May 27, 2025):
If you meant "directly to S3" then no, Koel won't be able to do that, and that's by design.
@iDomas commented on GitHub (May 28, 2025):
So what are my options? I tried koel lambda, but it throws error that aws-sdk not found. What are my options to fix this?
@phanan commented on GitHub (May 28, 2025):
To use Koel with S3, you simply upload your music through Koel's interface.
@iDomas commented on GitHub (May 28, 2025):
So it’s up to me how I allow more than 50mb upload size in docker-compose file? Is there a way without php.ini file that mounts on host volume?
@phanan commented on GitHub (May 28, 2025):
Max upload file size set by Koel's Docker is 800MB.
You can also try setting something like
php_value upload_max_filesize 512Min.htaccess.