#Kids Collection
1 messages · Page 1 of 1 (latest)
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
Welcome @heavy pasture!
Someone from <@&938443185347244033> will assist when they're available.
Including meta.log from the beginning is a huge help. Type !logs for more information.
After attaching your log, do not forget to hit the green check boxes when prompted by our bot.
You can press the "Close Post" button above or type /close at any time to close this post.
The following was shared by @heavy pasture and was automatically redacted by Luma as it may have contained sensitive information.
You have a reference in that config to Movies.yml
Copy that line and change it to Kids.yml or whatever the file is called.
Is movies.yml a default? is it in use now?
It is not a default; your config tells Kometa to read it.
I have no idea if you are actually using it.
libraries:
Movies:
remove_overlays: false
collection_files:
- default: basic
- default: imdb
- file: config/Movies.yml
TO
libraries:
Movies:
remove_overlays: false
collection_files:
- default: basic
- default: imdb
- file: config/Movies.yml
- file: config/Kids.yml # <<< ADDED
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
✅ YAML validation passed!! That is valid YAML, but may not meet Kometa's requirements
Tihs is my directory
under config
I dont know why theres another config directory under the config directory, but I do not have a movies.yml that I see
Then remove that line.
How do i force run it to see if it works?
Depends on how you are running it.
Actually, I should be trying to do this more on my own then ask you simple questions
i forgot how i did it since i set it up , im using docker in windows
modify this container, create a specific container, use docker run; the choice is yours, there is no single correct way.
thatll run everythying? if i jusdt want to update collections, id do --run-collections
If that's what the docs say.
Dont close this yet, im trying to figure out how to run it 😛
my knowledge is brutal. This is what I have running currently :
i Thought i could just click the run button, but obviously cant. I get a config error
I have no idea what that is.
One way would be to add the KOMETA_RUN environment variable to that container, then recreate it. It will then run immediately and exit.
Thats just a screenshot of docker for windows
If you want that container you have to remain running as it is now, then create a second container just like it with that env var set and use that second container for immediate runs.
And why would I want the container I have to remain runnign as it is now?
i cant wrap my head around docker. I thought the purpose is im running linux programs within windows
That container is probably waking up every day at some time [5 AM unless you've changed that] and processing your config.
Presumably you want that to continue.
So if i have it set to a schedule and do nothing, will it run the new collection whenever that schedule is set for?
Yes.
and i guess you dont use docker for windows. There is no way to just stop the container from running and restart it immediately?
so it runs the new config?
I do not think I want two of the same containers running simultaneously
If you set it up as I suggested that won't happen.
This is standard docker stuff; nothing specific to Windows
The Kometa container can run in one of two ways:
- stay running, wake up at a configured time, go back to sleep [your existing container]
OR - run right this second then exit. [the second container I am suggesting]
A single container can't do both.
This is the line i think i ran when i set it up " docker run --rm -it -v "c:/users/Bill/kometa/config:/config:rw" kometateam/kometa --run"
You could open a terminal into that container and run the screipt manualyl inside the container. That's a fourth route you could take.
and thats what that line does?
No, it's not. That command would create a new container, run the script, then exit and delete that container.
It would run everything, not just collections.
docker run -it -v "c:/users/Bill/kometa/config:/config:rw" kometateam/kometa
trying this
wish me luck
That's not going to do what you want.
📝 If you want to review this again, bbock727:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝
this work?
Author of Linked Message: BBock727
Person who Invoked the Command: BBock727
File Name: meta.log
Table of Contents:
Page 01: User Info
Page 02: Kometa Info
Page 03: Kometa Summary Info
Page 04: Kometa Config.yml YAML Validation ✅
Page 05: Plex Configuration - Section 1
Page 06: Plex Configuration - Section 2
Page 07: Rec 01 - ❌ ANIDB AUTH ERRORS
Page 08: Rec 02 - ❌🔒 BLANK API KEY ERROR
Page 09: Rec 03 - ❌ [ERROR]
Page 10: Rec 04 - ❌ MY ANIME LIST CONNECTION ERROR
Page 11: Rec 05 - ⚠️ [WARNING]
Page 12: Rec 06 - 💬💡️ PLEX DB CACHE ADVICE
Page 13: Rec 07 - 💬🪟🐧 WSL MEMORY RECOMMENDATION
--run-collections Kids
You're telling Kometa to run a collection named "Kids", and you don't have one of those.
You have a file called "Kids.yml", which contains four collections.
If you want to run everything that's in that file:
https://metamanager.wiki/en/latest/kometa/environmental/#run-files
Or if you want to run one of the collections defined in that file:
-- run-collections "Trending Kids Movies"
📝 If you want to review this again, bbock727:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝
Not sure it worked
you don't have a file named kids.yml, your file is named Kids.yml
Sure
antwanchild used !aenh
@heavy pasture, anything else needed here? If not, please type /close and hit enter. Please respond within 24 hours of this message or it will be archived.