Thinking of moving to a container for my main / ‘production’ beets instance. In theory it will be easier to move it between servers / devices, and allow it to play nice with other stuff on my NAS (similar to a python virtualenv).
Anyone have thoughts? Anyone using it currently? Looks like linuxserver is the only one actively supported.
I currently use a container with a custom Dockerfile for running beets on my NAS (easier than installing Python and a bunch of other dependencies). It probably doesn’t use many (or any) of the best practices when working with Docker but it suits my needs pretty well.
This allows me to just do ./beet.sh import /music/To\ Import without having to worry about messing with docker every time I run beets. This script could probably be improved somewhat in its volume mapping behaviour (maybe mapping the current working directory or doing something clever with argument parsing?), but it works well for my needs.
For context, my setup is that /mnt/user/music/Music contains my music library, with the configuration living at /mnt/user/music/Music/.beets. I’ve also got directory set in my beets configuration so that it points to /music/Music in the container.