| Time |
Nickname |
Message |
|
04:31
🔗
|
|
Odd0002 has quit IRC (Remote host closed the connection) |
|
08:09
🔗
|
|
Honno has joined #warrior |
|
13:33
🔗
|
|
yuitimoth has quit IRC (Remote host closed the connection) |
|
13:34
🔗
|
|
yuitimoth has joined #warrior |
|
14:17
🔗
|
|
nertzy2 has joined #warrior |
|
16:49
🔗
|
|
brannon has joined #warrior |
|
16:50
🔗
|
brannon |
exit |
|
16:51
🔗
|
|
braxxox has joined #warrior |
|
16:52
🔗
|
braxxox |
Hey there, i've been using the warrior docker container for a while and really love it. I recently realized that I could be running multiple concurrent warrior containers on my machine (e.g. 4-5 at the same time). Any reason not to do that? I don't want to spam. |
|
17:14
🔗
|
|
nertzy2 has quit IRC (Quit: This computer has gone to sleep) |
|
17:48
🔗
|
xmc |
usually we calibrate warrior jobs so that one worker container uses just short of one IP worth of ratelimiting |
|
17:48
🔗
|
xmc |
if you run multiple warriors on the same ip, they'll all get blocked |
|
18:48
🔗
|
braxxox |
Yeah that was my biggest fear. I've run three for an afternoon now, and no issues, but that could just be because of the project its working on (the archived site might have high IP limits or something) |
|
20:42
🔗
|
|
Pudsey has joined #warrior |
|
21:14
🔗
|
|
nertzy2 has joined #warrior |
|
21:30
🔗
|
|
SilSte has quit IRC (Remote host closed the connection) |
|
21:31
🔗
|
|
SilSte has joined #warrior |
|
21:33
🔗
|
|
Pudsey has quit IRC (Remote host closed the connection) |
|
21:54
🔗
|
|
Odd0002 has joined #warrior |
|
23:59
🔗
|
|
Honno has quit IRC (Read error: Operation timed out) |