vital badgerBOT
mutiny, please continue the conversation here.
Content: going back to my original post - opt/appdata/ is referenced but never explained. does this directory exist when running kometa? does it need to be configured? is this ./config:/config as defined in the kometa dockerconfig? not really questions for you since you are not my compsci teacher but more generic issues with the wiki
Attachments:(if any)
Welcome @vital badger!
It looks like you have not yet completed the id:customize section of our Discord server, this will allow us to help you quicker.
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.
vital badgerBOT
You can press the "Close Post" button above or type `/close` at any time to clos...
lapis vine
@tardy pewter moved your comment here
This is how the assets work. Posterizarr is just another tool created by a Kometa user that will essentially create assets for your media.
Do you have Kometa up and running? That needs to be so before posterizarr assets will ever be usable with Kometa
sharp geyser
I can't find "appdata" in the wiki, but generally paths like that are paths you create yourself..
When running in docker, Kometa will only create paths underneath /config inside the container, since it cannot see the host filesystem.
Something like this in docker-compose:
volumes:
- /path/to/config:/config
means "map the host directory /path/to/config to /config inside the container".
This means that your config.yml will be on your computer at /path/to/config/config.yml and Kometa will see it as /config/config.yml
Your asset directory will be on your computer at /path/to/config/assets and Kometa will see it as /config/assets