Timeline for Can you script Kodi (eg. Openelec) configuration such as upon a new deploy?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 27, 2017 at 2:03 | comment | added | HankCa | Great thanks for the feedback. I was thinking of a Docker image that could encapsulate the dependencies and just leave the configurable bits to file and directory paths. Generally though, I don't know much about the architecture but the problems you suggest make me think of code smells. | |
| Jan 26, 2017 at 23:50 | comment | added | goobering | Potentially tricky. As many Kodi add-ons have dependencies it may be difficult to pin down which files and folders need to be in place for which add-ons to function. I think you could do some pretty tedious legwork, put together a few different complete builds and choose between those, but I don't think that you're going to be able to pick and choose which individual packages are included in a given installation. There is the JSON API, but I can't see anything useful for you in there. | |
| Jan 26, 2017 at 23:09 | comment | added | HankCa | Yes thanks goobering - that certainly is a solution that works. Though I was hoping for some ability to script it so that deployments can be customised, such as servers that host media etc.... | |
| Jan 26, 2017 at 14:04 | history | answered | goobering | CC BY-SA 3.0 |