Replies: 1 comment 3 replies
-
|
The issue is the combination of these two settings: The first [ The second [ Kometa: If you can provide a log of any individual run, we can look at why it may not get to some other library. |
Beta Was this translation helpful? Give feedback.
-
|
Ar I see, that's pretty obvious now you say it :) I'll change that and give it another go :) |
Beta Was this translation helpful? Give feedback.
-
|
@chazlarson what is the ideal settings for this app? I assume you'd always want the container running but the actual script process running perhaps once every few days? If so how might you get that sort of setup or whatever is more ideal to work? I've made adjustments which meant it run through once fine, but it's now "exited - code 0" so I assume won't ever run again unless I start it? |
Beta Was this translation helpful? Give feedback.
-
|
There is no "ideal"; it's up to you. NOTE: These examples are minimal, showing only the required bits. Run immediately when the container starts, then exit the container: services:
kometa:
image: kometateam/kometa:latest
environment:
- KOMETA_RUN=true # << this makes it run-right-now-and-exit
volumes:
- /volume1/configs/kometa:/config:rwYou could Run in the background constantly, wake up once a day at 5AM, then go back to waiting: services:
kometa:
image: kometateam/kometa:latest
# no env var telling it to run means "wake up at 5AM every day"
volumes:
- /volume1/configs/kometa:/config:rwRun in the background constantly, wake up once a day at 1PM, then go back to waiting: services:
kometa:
image: kometateam/kometa:latest
environment:
- KOMETA_TIMES=13:00 # << this tells Kometa to wake up at 1PM instead of 5AM
volumes:
- /volume1/configs/kometa:/config:rwYou can schedule individual parts in the config, so if you want it to wake up every day at 5AM but only do TV on Monday and Movies on Tuesday or whatever, you'd schedule that in the config along with using one of the latter two composes above. Or, if you want to save resources and only run it on Friday at 3PM without it running all the time, you could use |
Beta Was this translation helpful? Give feedback.
-
Hey,
I'm running Kometa within Docker via Portainer. I'm not sure if it is an issue but it feels like one. When looking at my portainer log, it seems to never end, for days. Continuously outputting messages for different shows like this one:
No matter when I look it's always doing it, almost as if it's stuck in a loop. What's interesting is it never seems to get to my Movies.
Might anyone be able to see an issue or error with my setup?
Here is my Docker compose:
And here is my config.yml:
Many Thanks
Beta Was this translation helpful? Give feedback.
All reactions