Confused about directories when doing satellite setup

[einarpersson]

I have a laptop and a home server and I'm trying to get going with a satellite setup.

My understanding is that music_directory should be something like nfs://myhomeserver.local/data/external/media/music, i.e. a folder on the remote server. This is the (single) place where the actual music is.

But how about playlist_directory, should that also point to the remote server? My guess is yes, but an example is not provided in the satellite recipe in the docs.

I'm even more uncertain about the db_file and state_file. Do these belong to the remote mpd or the local mpd? Should I skip them in my local mpd config? Or add state_file but not db_file?

[subtlecaffeine]

music_directory points to however you're accessing the music. if you're doing it via the nfs:// URI or if it's mounted to a directory. It's just the directory where you music lives.

playlist_directory can live on the local system. It's just whatever the current playlist of your mpd is. The default should be fine.

db_file is handled through the database proxy in the configuration. That tells mpd to not just look at the server for the database, but to proxy update commands to it.

[einarpersson]

Thanks! And for completion: the state_file, is also for the local system, yes?

[subtlecaffeine]

Yes. the state_file keeps track of mpd's state when you shut it down so it can be restored.

Only things not on your local mpd in a satellite setup are the music and your database. Everything else stays on the system and will use the system defaults if not specified.