After ~10 minutes of running, I get this, then nothing else. I encountered this on 3 different containers processing 3 different streams. I'm assuming (based on timing) this is something to do with how you send a keep alive ping to the API.

INFO:     127.0.0.1:50234 - "POST /logs HTTP/1.1" 200 OK
{"timestamp":880.738,"text":"やばいこと言ってた。","translation":"I was saying something bad."}
INFO:     127.0.0.1:50264 - "POST /logs HTTP/1.1" 200 OK

INFO:     127.0.0.1:50264 - "POST /logs HTTP/1.1" 200 OK
INFO:     127.0.0.1:50300 - "GET /static/index.html HTTP/1.1" 304 Not Modified
INFO:     127.0.0.1:50300 - "GET /static/index.js HTTP/1.1" 304 Not Modified
INFO:     127.0.0.1:50300 - "GET /env HTTP/1.1" 200 OK
{SESSION KEY}
INFO:     127.0.0.1:50300 - "POST /logs HTTP/1.1" 200 OK

I don't know if the session key that was printed here is the same key as the one that was obtained before or not.

I'd like to be able to limit how many system resources the KT runner is allowed to consume. Something like MAX_CPU and MAX_MEM where mem accepts a percent or a unit. I also would like a system variant (MAX_SYS_CPU and MAX_SYS_MEM) that prevents the runner from starting new containers if the system wide utilization would exceed those values.
The runner should also probably default to some sane values (i.e. 50% for runner specific, and 80% for system wide)and check to ensure that there is enough to run a single container (i.e. > 5% CPU, > 500MB memory).

A network utilization limit may also be nice for other people hosting the runner on slower connections, but this is probably lower priority since the network utilization seems rather low anyways.

example:

MAX_CPU=60%
MAX_SYS_CPU=90%
MAX_MEM=50%
MAX_SYS_MEM=80%

or

MAX_MEM=8192MB
MAX_SYS_MEM=80%

or

MAX_MEM=8GB
MAX_SYS_MEM=16GB

As far as I understand, currently the API URL is hardcoded to api.livetl.app, however I'd like to be able to run Kanatran to test my local development instance of the API.
Something as simple as API_URL='localhost' in .env, then fallback to api.livetl.app when not present would be good enough for me.

Mentioned in #9 . Limit the host usage, maybe using https://github.com/pitrho/docker-host-stats

Environment is purely Docker on Windows (no WSL), cloned using Git for Windows (which presumably defaults to CRLF). Potentially more issues present when other files are also using CRLF.

PS > docker --version ; docker-compose --version
Docker version 19.03.8, build afacb8b
docker-compose version 1.25.5, build 8a1c60f6
PS > docker-compose run -d -e VIDEO=xHP6lpOepk4 --name KTest watcher
KTest
PS > docker ps -a -f "name=KTest"
IMAGE       COMMAND                  CREATED             STATUS                     NAMES
watcher     "bash /usr/src/watch…"   4 minutes ago       Exited (2) 4 minutes ago   KTest
PS > docker logs KTest
/usr/src/watcher/kanatran.bash: line 2: $'\r': command not found
/usr/src/watcher/kanatran.bash: line 4: syntax error near unexpected token `$'{\r''
'usr/src/watcher/kanatran.bash: line 4: `function log() {