Hi all,
I want to create an LMS Docker build-and-run that works "out of the box" without having to add additional configuration through the UI between container restarts. In particular, I'm looking at Spotty, which has an authentication step in the UI where you enter username and password. I recall that it says in one of the Spotty forum posts that the password isn't stored anywhere in LMS and indeed from wandering through the Spotty configuration files I can't find either a password or any recognisable auth tokens. I also found some posts with DEBUG log output of running the `spotty-x86_64` binary and I can't see anything in those command lines that contain tokens or passwords either. I suppose I'm hoping that I can derive a token (once) and keep it somewhere safe, and then inject it into my container on runtime perhaps as an environment variable. I'm just not sure how possible this is - I would expect a Spotify token to expire but obviously Spotty manages this somehow without storing a password. Can anybody suggest any further docs or reverse engineering I can try to figure this out? Thanks, Peter ------------------------------------------------------------------------ psaffrey's Profile: http://forums.slimdevices.com/member.php?userid=66276 View this thread: http://forums.slimdevices.com/showthread.php?t=111454 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
