starred/koel-koel

Fork 0

mirror of https://github.com/koel/koel.git synced 2026-04-25 00:36:03 +03:00

directory #715

New issue

Closed

opened 2026-02-26 02:34:03 +03:00 by kerem · 6 comments

kerem commented

2026-02-26 02:34:03 +03:00

Owner

Originally created by @gramakri on GitHub (Nov 10, 2020).
Original GitHub issue: https://github.com/koel/koel/issues/1254

Describe the bug
Koel attempts to write to /public/img/covers .

Environment

Koel version [e.g. v4.1.0]
OS: Cloudron package
Browser [e.g. Chrome 79]
PHP version [e.g. v7.2.0]
Node version [e.g. v10.15.3]

Additional context
I am creating a Koel package for Cloudron at https://git.cloudron.io/cloudron/koel-app . On Cloudron, the app is deployed in containers with a readonly filesystem. This means that the application directories are not writable (one has to explicitly mark them as such). It seems Koel writes to /public/img/covers directory. Is this directory meant to be writable by the web application. Same goes for /public/img/artists. Is that directory meant to be writable by the app? Or is it that the entire /public should be writable by the app?

Thanks!

Originally created by @gramakri on GitHub (Nov 10, 2020). Original GitHub issue: https://github.com/koel/koel/issues/1254 **Describe the bug** Koel attempts to write to `/public/img/covers` . **Environment** - Koel version [e.g. v4.1.0] - OS: Cloudron package - Browser [e.g. Chrome 79] - PHP version [e.g. v7.2.0] - Node version [e.g. v10.15.3] **Additional context** I am creating a Koel package for Cloudron at https://git.cloudron.io/cloudron/koel-app . On Cloudron, the app is deployed in containers with a readonly filesystem. This means that the application directories are not writable (one has to explicitly mark them as such). It seems Koel writes to `/public/img/covers` directory. Is this directory meant to be writable by the web application. Same goes for `/public/img/artists`. Is that directory meant to be writable by the app? Or is it that the entire `/public` should be writable by the app? Thanks!

kerem

2026-02-26 02:34:03 +03:00

closed this issue
added the
Documentation
label

kerem commented

2026-02-26 02:34:04 +03:00

Author

Owner

@gramakri commented on GitHub (Nov 10, 2020):

Relevant forum post - https://forum.cloudron.io/topic/3582/production-error-laravel-log

@gramakri commented on GitHub (Nov 10, 2020): Relevant forum post - https://forum.cloudron.io/topic/3582/production-error-laravel-log

kerem commented

2026-02-26 02:34:04 +03:00

Author

Owner

@BrookeDot commented on GitHub (Dec 30, 2020):

We should likely update the install documentation, to note that public/img/covers/ (and maybe public/img/* ) should be writable. There's also a bit more info on permissions in #667

@BrookeDot commented on GitHub (Dec 30, 2020): We should likely update the install documentation, to note that `public/img/covers/` (and maybe `public/img/*` ) should be writable. There's also a bit more info on permissions in #667

kerem commented

2026-02-26 02:34:04 +03:00

Author

Owner

@gramakri commented on GitHub (Dec 30, 2020):

@BrookeDot Should we create empty directories like public/img/covers etc with .gitignore ? At https://github.com/koel/koel/tree/master/public

@gramakri commented on GitHub (Dec 30, 2020): @BrookeDot Should we create empty directories like `public/img/covers` etc with .gitignore ? At https://github.com/koel/koel/tree/master/public

kerem commented

2026-02-26 02:34:04 +03:00

Author

Owner

@phanan commented on GitHub (Dec 30, 2020):

I'm not familiar with Cloudtron, but Koel should be able to write to public (for manifests and media metadata) and storage (for logs, library backups, and search indexes in the next major version).

@phanan commented on GitHub (Dec 30, 2020): I'm not familiar with Cloudtron, but Koel should be able to write to `public` (for manifests and media metadata) and `storage` (for logs, library backups, and search indexes in the next major version).

kerem commented

2026-02-26 02:34:04 +03:00

Author

Owner

@gramakri commented on GitHub (Dec 31, 2020):

@phanan Thanks for your response. I am wondering how update should work since public/ already has sw.js and an index.php which seems to be code and not data. Is the idea that one should replace these two files when updating koel but keep the rest? What if other code files get put in there in the future? Thanks.

@gramakri commented on GitHub (Dec 31, 2020): @phanan Thanks for your response. I am wondering how update should work since public/ already has sw.js and an index.php which seems to be code and not data. Is the idea that one should replace these two files when updating koel but keep the rest? What if other code files get put in there in the future? Thanks.

kerem commented

2026-02-26 02:34:04 +03:00

Author

Owner

@phanan commented on GitHub (Dec 31, 2020):

When updating Koel you should expect any file to be replaceable. Hence, I'm not sure what Cloudtron's readonly mode is.

@phanan commented on GitHub (Dec 31, 2020): When updating Koel you should expect _any file_ to be replaceable. Hence, I'm not sure what Cloudtron's readonly mode is.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/koel-koel#715

No description provided.

Rows
Columns