[pkscout]

I have deployed a docker-compose version with MariaDB container and the issue I encounter is there are some missing settings: http control are not where they are in a regular Kodi installation
Kodi-Headless:


Regular Kodi (on Windows):

You might need to check the settings level on Kodi running in the Docker container.  By default Kodi has settings set to "standard" which hides a bunch of things.  My bet is on your Windows install you set it to Advanced or Expert.  In the web interface when you go to settings, check the ADVANCED OPTIONS in the WEB INTERFACE section.  There is a drop down for setting level that you can change.  That might expose those other settings.

[matthuisman]

yes, could be that as well
Also, Linux settings are slightly different to Windows

[john_matrix]

In fact, at the beginning, I thought to delocate the movies scrapping to an "always-on" device.
This way, I don't have to wait for the box to scrap everything by itself (it can take some minutes) when Kodi is launched.

But as I can't find the same settings in your container, I secondly thought to use a "primary" device to scrape the collections and send the updated data to the Kodi container.

Maybe I am wrong in my reasoning?

I have another idea to configure a kodi from a Windows computer and when everything is done, copy the userdata folder to the container?

[matthuisman]

kodis web ui cant do everything. it cant set content etc for starters.
So often you do need to set it up on another client first and then copy the userdata

the readme even mentions this
https://github.com/matthuisman/docker-ko...pplication

"If you intend to use this kodi instance to perform library tasks other than merely updating, eg. library cleaning etc, it is important to copy over the sources.xml from the host machine that you performed the initial library scan on to the userdata folder of this instance, otherwise database loss can and most likely will occur."

[john_matrix]

Thanks for the clarification ;-)

[john_matrix]

Thank you for your suggestion but even with expert settings selected, some settings are missing
I will follow the recommendation of Matthuisman and configure a regular Kodi and transfer the conf to the container ;-)

[john_matrix]

I have deployed a docker-compose version with MariaDB container and the issue I encounter is there are some missing settings: http control are not where they are in a regular Kodi installation
Kodi-Headless:


Regular Kodi (on Windows):

You might need to check the settings level on Kodi running in the Docker container.  By default Kodi has settings set to "standard" which hides a bunch of things.  My bet is on your Windows install you set it to Advanced or Expert.  In the web interface when you go to settings, check the ADVANCED OPTIONS in the WEB INTERFACE section.  There is a drop down for setting level that you can change.  That might expose those other settings.

Thank you for your suggestion but even with expert settings selected, some settings are missing 
I will follow the recommendation of Matthuisman and configure a regular Kodi and transfer the conf to the container ;-)

[loucao_jr]

Hi!

First of all, thanks for your docker!! 

I've deployed it and it's working great beside not scanning the library automatically for updates, It's suppose to do it, right? If I hit  "Scan video library" It runs great and updates everything accordingly... What am I missing?! A peace of the follows 
 

Code:

2024-10-01 17:42:38.929 T:183 info <general>: WebSocket: connection closed by client
2024-10-01 17:42:39.003 T:183 info <general>: JSONRPC Server: Disconnection detected
2024-10-01 17:43:26.996 T:174 info <general>: Samba is idle. Closing the remaining connections
2024-10-01 22:52:57.987 T:183 info <general>: JSONRPC Server: New connection added
2024-10-01 22:53:09.600 T:7589 info <general>: VideoInfoScanner: Starting scan ..

Another question, can I use Trakt add-on with the headless kodi? Searched with no success... 

Thanks

[john_matrix]

Hello,

For automatic scanning, I have installed the addon libraryautoupdate and set a scan every 15 minutes.
Don't know for the Trakt addon but I would say yes but as it track your views, maybe it's better to install it on the Kodi "client"?

[loucao_jr]

Thanks!! I'm looking into it.

[bossanova808]

Another way of tackling regular library updates is to use cron to hit the jsonrpc periodically, e.g. here's a call to do a full library update twice a day:

Code:


12 3,15 * * * chronic curl --data-binary '{ "jsonrpc": "2.0", "method": "VideoLibrary.Scan", "id": "mybash"}' -H 'content-type: application/json;' http://kodi:[email protected]:8081/jsonrpc


(...actually I guess this is what you may already be doing, but I find it easier/more controllable than configuring an addon in the container so will leave this here in case others are looking for solutions).

[matthuisman]

yup, kodi itself has no autoupdate mechanism - so just leave it upto the user to do it however they need
I personally have a script that calls the API method to do update after I add new content.
But autoupdate would also be neat

Looks like some good options above

As for trakt - I think that polls what your playing. Your headless wont be playing anything so dont think itll work
As above - install that on your actual clients that play content

[HeresJohnny]

Another way of tackling regular library updates is to use cron to hit the jsonrpc periodically, e.g. here's a call to do a full library update twice a day:

Code:


12 3,15 * * * chronic curl --data-binary '{ "jsonrpc": "2.0", "method": "VideoLibrary.Scan", "id": "mybash"}' -H 'content-type: application/json;' http://kodi:[email protected]:8081/jsonrpc


http:// and not smb:// ? That sounds kinda slow... have you benchmarked the alternatives by any chance?

[bossanova808]

It's an http request to the JSON RPC API telling Kodi to kick off a library scan.  The actual scan, of course, will use whatever your library uses (in my case NFS).