Skip to content

fix: let Koel serve the PWA manifest #231

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
phanan merged 2 commits into from
Sep 9, 2026
+4 −6
Merged

fix: let Koel serve the PWA manifest #231

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e8205bf
fix: let Koel serve the PWA manifest
phanan Sep 9, 2026
22348c1
docs: mention the remote controller manifest in the changelog
phanan Sep 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,10 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).

Since this docker image only has one tag which is `latest`, there are no versions. However we'll write changes with the date at which they occured.

## 2026-09-09
### Fixed
- Koel now creates the manifests (the files that let you install Koel as an app) at `/manifest.json` and `/manifest-remote.json`. The `start_url` value comes from `APP_URL`. The name comes from your custom name on Koel Plus. Before this change, the files held a placeholder address `https://your.koel.host`. You do not have to edit or bind-mount the file. To keep a manifest that you wrote, bind-mount it over `/var/www/html/public/manifest.json`, and Koel serves your file instead.

## 2026-05-22
### Fixed
- ⚠ Image storage path moved to follow koel/koel#2479. If you're upgrading from a previous release, update your `docker-compose.yml` so the `image_storage` volume binds to `/var/www/html/storage/app/public/images` instead of `/var/www/html/public/img/storage`. Existing data in your `image_storage` volume / host bind transfers over automatically when you switch the mount point — files inside the volume don't move, only the mount path inside the container does.
Expand Down
1 change: 0 additions & 1 deletion Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -101,7 +101,6 @@ RUN a2enmod rewrite

# Copy the downloaded release
RUN cp -R /tmp/koel/. /var/www/html \
&& mv /var/www/html/public/manifest.json.example /var/www/html/public/manifest.json \
# The release tarball ships public/storage as an absolute symlink into the path the
# release runner built it at, which resolves nowhere here and leaves koel unable to read
# or write uploaded images. Replace it with a relative link to the same target.
Expand Down
5 changes: 0 additions & 5 deletions goss.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,11 +15,6 @@ file:
owner: www-data
group: www-data
filetype: directory
/var/www/html/public/manifest.json:
exists: true
owner: www-data
group: www-data
filetype: file
/var/www/html/.git:
exists: false
/var/www/html/.github:
Expand Down
Loading