- Melbourne, AU
- https://pharaohgraphy.com
-
Decolonize EVERYTHING! 🫂
- Joined on
2025-10-31 -
-
590fab5c57
Merge pull request 'chore: release 0.2.0+0.58.0' (#3) from pharaohgraphy/recipe-navidrome:0.2.0+0.58.0 into main
Thanks for your feedback all, I've fixed this with a backwards-compatible EXTRA_VOLUME env var and updated the README accordingly 🙏
Can we use something like
EXTRA_VOLUMEhttps://git.coopcloud.tech/coop-cloud/jellyfin/src/branch/main/compose.yml#L14? we will need to have a second compose file to override the volume mounted…
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…
abra app deploy handles re-deploy and shows env updates
My 2c is Abra should be 'smarter' about this rather than gung-ho, here's what I envision SHOULD work based on what I've tried manually in the server's CLI via docker service .. commands:
1.…
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…
abra app config -> abra app env edit
Config is confusing as they are simply Docker env vars, we aren't trying to pull over people's eyes and we want this ecosystem to be as transparent & friendly as possible, so I would say we should…
abra app deploy handles re-deploy and shows env updates
@decentral1se you're correct, the confusion stems from the fact that Abra calls it config but Docker is just injecting Env vars... not sure it's worth renaming, it would be a breaking change…