December 16, 201411 yr I'm trying to make XBMC-headless server docker more appliance like to end up with it being installed and the setup files customised per user via template from a repo but am stumbling at the first hurdle with two problems, my less than stellar linux skills and something that's particular to the docker way of things. A bit of background, creating a new XBMC-headless instance within a VM I can utilise my current settings right off the bat just by putting the files required manually into ~/.xbmc folder. Trying to do things the docker way is a little different since the .xbmc folder or opt/...... if running portable don't get created until XBMC has run for the first time. I've tried calling scripts in the build stage to start XBMC, wait and then stop to create the folders, i've tried a start script for the container to copy over files on start of the container, basically XBMC seems intent on creating it's folders on the first run of the container every time. if i stop/start the container the files still don't get copied across. I know these are vague terms i have given here but can some guru type point me in the right direction please. EDIT- solved it, turns out to be really simple, move the whole set of folders across before the xbmc-headless runs, lol.
December 17, 201411 yr Something to also consider. If you use mysql and have a collection already a new XBMC instance will download ALL the art again from the internet unless you copy up the artwork and the textures sqlite database before you connect it to mysql.
December 17, 201411 yr Author Something to also consider. If you use mysql and have a collection already a new XBMC instance will download ALL the art again from the internet unless you copy up the artwork and the textures sqlite database before you connect it to mysql. Yeah that can be a real pain, i personally export mine to the movie folders within xbmc itself and don't worry too much about the headless instance getting art. for people on a data allowance though, it could definitely be a factor.
December 17, 201411 yr Author Something to also consider. If you use mysql and have a collection already a new XBMC instance will download ALL the art again from the internet unless you copy up the artwork and the textures sqlite database before you connect it to mysql. As an aside though, this is still gotham based version, when helix goes final the changes between the two will be minimal in terms of the Dockerfile itself (will need a recompile, but that's my problem, lol) , basically just change the git pull to helix and a different patch to enable it to run headless, the dependencies are the same. people are going to have to rescan their libraries for helix, because of the change in database version in xbmc/kodi.
December 17, 201411 yr No rescan necessary Helix upgrades the dbase and keeps a copy of the old one as well.
December 17, 201411 yr Author No rescan necessary Helix upgrades the dbase and keeps a copy of the old one as well. damn, different from the change from eden to frodo and frodo to gotham.
December 17, 201411 yr All those versions upgraded the dbase in the same way and from memory frodo even modified the artwork on disk crc filing system. On that note Helix changes the on disk xbmc folder name to kodi as well. I have a large library and i havent needed to rescan content in multiple years and dozens of XBMC nighlity version changes
December 17, 201411 yr Author i have about 6000 or so movies. i rescanned every version change, guess i won't this time, lol.
Archived
This topic is now archived and is closed to further replies.