coop-cloud/navidrome
1
1
Fork 0
Code Issues Pull Requests 2 Actions Packages Projects Releases Wiki Activity

chore: release 0.2.0+0.58.0 #3

Merged
pharaohgraphy merged 1 commits from :0.2.0+0.58.0 into main 2025-11-06 09:55:28 +00:00
Conversation 5 Commits 1 Files Changed 5 +17 -4
5 changed files with 17 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
.drone.yml
View File

@ -17,6 +17,7 @@ steps:
DOMAIN: {{ .Name }}.swarm-test.autonomic.zone
STACK_NAME: {{ .Name }}
LETS_ENCRYPT_ENV: production
EXTRA_VOLUME: "/dev/null:/tmp/.dummy"
trigger:
branch:
- main

3
.env.sample
View File

@ -2,6 +2,9 @@ TYPE=navidrome
DOMAIN=navidrome.example.com
# ! If your files live on the host already, make sure to bind the directory below
EXTRA_VOLUME="/dev/null:/tmp/.dummy"
## Domain aliases
#EXTRA_DOMAINS=', `www.navidrome.example.com`'

5
README.md
View File

@ -5,7 +5,7 @@
<!-- metadata -->
* **Category**: Apps
* **Status**: 0
* **Status**: 2
* **Image**: [`navidrome`](https://hub.docker.com/r/navidrome), 4, upstream
* **Healthcheck**: No
* **Backups**: No
@ -17,8 +17,9 @@
## Quick start
* `abra app new navidrome --secrets`
* `abra app new navidrome`
* `abra app config <app-name>`
* Make sure to update the `EXTRA_VOLUME` env var if you have files on the host already, then you can [add them within the Navidrome UI later](https://www.navidrome.org/docs/usage/multi-library/#creating-additional-libraries)
* `abra app deploy <app-name>`
For more, see [`docs.coopcloud.tech`](https://docs.coopcloud.tech).

5
compose.yml
View File

@ -3,12 +3,13 @@ version: "3.8"
services:
app:
image: deluan/navidrome:pr-3349
image: deluan/navidrome:0.58.0
networks:
- proxy
volumes:
- navidrome_data:/data
- navidrome_music:/music:ro
decentral1se marked this conversation as resolved Outdated
decentral1se commented 2025-11-04 23:33:55 +00:00
Outdated
Review
Copy Link

Should it not be: "navidrome_music:${MUSIC_PATH_HOST}:ro"?

This is pretty unconventional but I can see why you'd want to customise this.

Does it work? We ran into related issues lately: toolshed/abra#492

Should it not be: `"navidrome_music:${MUSIC_PATH_HOST}:ro"`? This is pretty unconventional but I can see why you'd want to customise this. Does it work? We ran into related issues lately: https://git.coopcloud.tech/toolshed/abra/issues/492
pharaohgraphy commented 2025-11-04 23:46:44 +00:00
Outdated
Review
Copy Link

Other way around, your suggestion would do the following:

  • Always use a Docker volume navidrome_music
  • Allow the env var to control where that's mounted to on the container

My change allows you to set a path to your music folder on the host.
And yes it works 💯

Other way around, your suggestion would do the following: - Always use a Docker volume `navidrome_music` - Allow the env var to control where that's mounted to **on the container** My change allows you to set a path to your music folder on the host. And yes it works 💯
decentral1se commented 2025-11-04 23:59:46 +00:00
Outdated
Review
Copy Link

Huh, I thought docker swarm didn't support that kind of syntax. Another issue with this is that it breaks volume support for other maintainers (navidrome_music dissapears from one version to the next). You can create a separate compose.hostvol.yml and do your own stuff there without disrupting the main config for the others. See https://docs.coopcloud.tech/maintainers/handbook/#optional-compose-files and the other recipes as examples of how to approach this.

Huh, I thought docker swarm didn't support that kind of syntax. Another issue with this is that it breaks volume support for other maintainers (`navidrome_music` dissapears from one version to the next). You can create a separate `compose.hostvol.yml` and do your own stuff there without disrupting the main config for the others. See https://docs.coopcloud.tech/maintainers/handbook/#optional-compose-files and the other recipes as examples of how to approach this.
👀 1
pharaohgraphy commented 2025-11-05 00:03:26 +00:00
Outdated
Review
Copy Link

Why wouldn't it work? Docker binding/volume syntax is all the same no?

Valid point re: backwards-compat. upon updating though, I didn't think of that, but I'm 50/50 on the optional compose file because it makes NO sense to me to create a new docker volume for the music folder and make it read-only.

That means you'd have to manually mount the volume on another service to upload/add content... which is cumbersome & probs not the ideal use-case?

The binding mount makes a lot more sense as a default option, just like Jellyfin 🤷 so you can use a shared drive or anything else you like on the host to make the media populated & available.

Am I missing something here? 🙃

Why wouldn't it work? Docker binding/volume syntax is all the same no? Valid point re: backwards-compat. upon updating though, I didn't think of that, but I'm 50/50 on the optional compose file because it makes NO sense to me to create a new docker volume for the music folder and make it read-only. That means you'd have to manually mount the volume on another service to upload/add content... which is cumbersome & probs not the ideal use-case? The binding mount makes a lot more sense as a default option, just like Jellyfin 🤷 so you can use a shared drive or anything else you like on the host to make the media populated & available. Am I missing something here? 🙃
decentral1se commented 2025-11-05 00:09:38 +00:00
Outdated
Review
Copy Link

Let's see what the other maintainers think, @cas @ammaratef45?

Let's see what the other maintainers think, @cas @ammaratef45?
👍 1
pharaohgraphy commented 2025-11-06 03:42:35 +00:00
Outdated
Review
Copy Link

Thanks for your feedback all, I've fixed this with a backwards-compatible EXTRA_VOLUME env var and updated the README accordingly 🙏

Tested on my own navidrome stack ✅

Thanks for your feedback all, I've fixed this with a backwards-compatible `EXTRA_VOLUME` env var and updated the README accordingly 🙏 Tested on my own `navidrome` stack ✅
❤️ 1
- "${EXTRA_VOLUME}"
environment:
ND_SCANSCHEDULE: 1h
ND_LOGLEVEL: info
@ -26,7 +27,7 @@ services:
- "traefik.http.routers.${STACK_NAME}.middlewares=${STACK_NAME}-redirect"
- "traefik.http.middlewares.${STACK_NAME}-redirect.headers.SSLForceHost=true"
- "traefik.http.middlewares.${STACK_NAME}-redirect.headers.SSLHost=${DOMAIN}"
- "coop-cloud.${STACK_NAME}.version=0.1.0+pr-3349"
- "coop-cloud.${STACK_NAME}.version=0.2.0+0.58.0"
networks:
proxy:

7
release/0.2.0+0.58.0 Normal file
View File

@ -0,0 +1,7 @@
## Navidrome Docker image
Bumped to latest version-tagged image: v0.58.0
## Configuration
Add support for an `EXTRA_VOLUME` to be mounted & instructions on how to setup a multi-library