Igor Ivanov
Igor Ivanov
@runabol could you take a look?
Really useful feature: we have a really big queue of parallel tasks in the many jobs. But if some urgent task appears - we can't move it to the beggining...
Thanks for the pointing to this. As I can see - https://github.com/runabol/tork/blob/main/configs/sample.config.toml#L39-L45 Here some values. But could you share the link to documentation which describes in more details what that...
Thanks @runabol It helped a lot. Please add more info to the documentation - you will avoid a lof of questions in the future
I have to reopen this: We really need option to disable logging. Take a look - we set option in the logs: ``` [datastore.postgres] dsn = "" task.logs.interval = "168h"...
If you check my message above - this option doesn't work Today I've checked logs in DB and I see ``` tork=# select min(created_at) from tasks_log_parts; min ---------------------------- 2024-04-22 12:42:13.105112...
If I'm not mistaken - we have about 20 millions of rows per day in DB
I have some secrets in the POD, so I don't want to set those secrets like passwords or connection strings directly in Tork Job. I want tork worker to fetch...
It could help but is it possible to insert all env vars or env vars by prefix? POD could be restarted and fetch new ENV from secret and ConfigMap and...
@runabol could you correct me? I set this in the config: ``` tork-worker-7998c84f98-nf96k:/# cat /etc/tork/config.toml ... [middleware.task.hostenv] vars = ["SOME_ENV"] ``` I can see this env inside host env ```...