02:45:00Aoede quits [Quit: ZNC - https://znc.in]
02:45:22Aoede (Aoede) joins
08:01:23Chris50102 (Chris5010) joins
08:02:56Chris5010 quits [Ping timeout: 252 seconds]
08:02:56Chris50102 is now known as Chris5010
08:29:57@rewby quits [Ping timeout: 265 seconds]
09:41:18Chris50105 (Chris5010) joins
09:42:56Chris5010 quits [Ping timeout: 265 seconds]
09:42:56Chris50105 is now known as Chris5010
11:35:52rewby (rewby) joins
11:35:52@ChanServ sets mode: +o rewby
11:57:02G4te_Keep3r3492 quits [Ping timeout: 252 seconds]
12:05:04G4te_Keep3r3492 joins
12:42:15PredatorIWD joins
12:42:29PredatorIWD quits [Remote host closed the connection]
17:24:04Pingerfowder quits [Quit: ZNC - https://znc.in]
17:24:55Pingerfowder (Pingerfowder) joins
18:29:38yano1 quits [Client Quit]
18:33:40yano (yano) joins
18:34:19Dango360 (Dango360) joins
18:35:14_Dango360 quits [Ping timeout: 252 seconds]
18:55:35systwi quits [Ping timeout: 252 seconds]
19:14:28<fireonlive>is there recommended minimum disk space for the docker warriors? if i were to slip a couple around in places?
20:36:53Meli quits [Ping timeout: 265 seconds]
20:38:14Meli (Meli) joins
20:56:38<TheTechRobo>fireonlive: I'd suggest at least 5GiB for small projects, but that's VERY generous; large projects (e.g. ones that archive video) would probably benefit from a bit more. But if your concurrency is low it should be fine - just make sure you set a Docker log limit, otherwise the logs get huge.
20:57:11<TheTechRobo>If an item is too big, it'll just fail, so another Warrior will pick it up, so it doesn't matter too much if your Warrior is too small for the occasional item, but you don't want 99% of items failing bc they're too big.
20:57:51<TheTechRobo>In my experience, you probably don't need 5GiB for most projects, but better safe than sorry.
20:59:45<fireonlive>ah, that makes sense and thanks for the tip on the logs there :D
23:04:47@rewby quits [Ping timeout: 265 seconds]