00:00:37lorwp quits [Ping timeout: 258 seconds]
00:00:39dm4v quits [Read error: Connection reset by peer]
00:01:26<h3ndr1k>Did anyone here setup a distributed Smokeping before? The CGI keeps deleting and rewriting some temporary files, which changes their permissions and then it complains about not being able to lock them.
00:03:39dm4v joins
00:03:41dm4v quits [Changing host]
00:03:41dm4v (dm4v) joins
00:07:31Arcorann__ joins
00:09:55BlueMaxima joins
00:09:57BlueMaxima_ joins
00:26:27BlueMaxima_ quits [Client Quit]
00:26:27BlueMaxima quits [Client Quit]
00:41:07lorwp (lorwp) joins
01:02:48dm4v_ joins
01:04:15dm4v quits [Ping timeout: 258 seconds]
01:04:15dm4v_ is now known as dm4v
01:04:15dm4v quits [Changing host]
01:04:15dm4v (dm4v) joins
01:06:33fofofofofofofofo quits [Ping timeout: 258 seconds]
01:29:29Arcorann__ quits [Read error: Connection reset by peer]
01:30:13Arcorann__ joins
01:30:23monoxane quits [Quit: Ping timeout (120 seconds)]
01:30:27driib quits [Quit: Ping timeout (120 seconds)]
01:30:36monoxane (monoxane) joins
01:30:40driib (driib) joins
01:32:32psy quits [Ping timeout: 244 seconds]
01:47:48psy (psy) joins
02:32:05Krownest1 (Krownest) joins
02:35:52Krownest quits [Ping timeout: 258 seconds]
02:41:31Krownest1 quits [Read error: Connection reset by peer]
02:52:46G4te_Keep3r quits [Quit: The Lounge - https://thelounge.chat]
02:56:20G4te_Keep3r joins
03:01:00G4te_Keep3r quits [Client Quit]
03:06:13G4te_Keep3r joins
03:40:52qw3rty_ joins
03:44:44qw3rty__ quits [Ping timeout: 250 seconds]
03:56:50Krownest (Krownest) joins
04:15:14<Krownest>Is there a way to configure my servers to automatically pull and start new docker images for new projects?
04:46:18mutantmonkey quits [Remote host closed the connection]
04:46:39mutantmonkey (mutantmonkey) joins
05:02:15DogsRNice quits [Read error: Connection reset by peer]
05:32:12mutantmonkey quits [Ping timeout: 258 seconds]
05:32:35mutantmonkey (mutantmonkey) joins
05:56:42Atom-- quits [Read error: Connection reset by peer]
05:57:15Atom joins
06:12:48<rewby>Krownest: you can use the warrior docker container. It'll auto select jobs, just like the vm version does
07:02:17HP_Archivist quits [Ping timeout: 258 seconds]
07:42:17fofofofofofofofo joins
07:50:09AK quits [Remote host closed the connection]
08:06:12AK (AK) joins
08:21:09<kiska>https://server8.kiska.pw/uploads/3a563ef647c898f3/image.png lol
08:21:19<kiska>It costs them more to process this payment :D
09:11:58HP_Archivist (HP_Archivist) joins
09:27:02HP_Archivist quits [Read error: Connection reset by peer]
11:24:51@EggplantN quits [Quit: Ping timeout (120 seconds)]
11:25:26EggplantN joins
11:41:45EggplantN quits [Changing host]
11:41:45EggplantN (EggplantN) joins
11:41:45@ChanServ sets mode: +o EggplantN
14:41:54lunik1 quits [Ping timeout: 258 seconds]
15:25:00Hackerpcs quits [Ping timeout: 250 seconds]
15:32:22lunik1 joins
15:37:59spirit joins
16:07:02Arcorann__ quits [Ping timeout: 250 seconds]
16:18:25Hackerpcs (Hackerpcs) joins
16:38:25<Krownest>I meant more so projects that end quickly, like codeplex or gree, were those warrior projects?
16:40:57<Jake>I think codeplex had an issue with warrior, but they are almost always warrior projects too
16:49:42qwertyasdfuiopghjkl joins
17:19:20<Krownest>Since I run docker images for individual projects right now (reddit, urls, pastebin, etc) can I set up the warrior docker image to ignore certain projects so I don't duplicate what I'm already working on?
17:20:45<Jake>The warrior docker project allows you to select specific projects, or 'warriors choice' (wherever help is currently needed)
17:30:53<Krownest>Warrior's choice sounds fine, but I don't want it to run Warrior's choice on a project which I'm already running docker images for on the same machine. Also, are new projects automatically added to warriors choice, cause if not it wouldn't make sense for me to use it I would think.
17:31:56<@EggplantN>Tracker admins ( 👋 ) set the "AT Choice", it can't see the docker containers from outside so it doesn't know, you wouldn't be duplicating any actual work, just contributing more
17:32:26<@EggplantN>new projects are automatically added to the warrior, if we believe we need the warriors help, we change the choice to that project
17:32:38<@EggplantN>But in the case of some recent projects, we've completed the project fast enough
17:33:11<Krownest>So would it make more sense for me to make something to watch the github repo and automatically add new -grab projects as they come in rather than use the warrior?
17:33:45<@EggplantN>Docker images aren't always immediately built. Plus how would you know what concurrency to run?
17:33:58<Krownest>I would probably just default it to 2.
17:34:00<@EggplantN>Some projects you can run 20/IP, others 1/IP (github-grab previously)
17:34:21<Krownest>As 2 is always used as the default in the documentation for the -grab projects.
17:34:42<Krownest>Then in the future if I learn later that we can run at a higher concurrency, then just up it later.
17:35:36<Krownest>I just don't want to miss out on new projects lol, but then again, I guess if the project is completed in 6 hours or less before I even noticed it's a project, I guess it was small enough not to need everyone's help in the first place lol.
17:41:56DogsRNice (Webuser299) joins
17:42:39DogsRNice quits [Remote host closed the connection]
17:52:25<@EggplantN>thats the thinking Krownest we will always enable warriors if we feel the need
18:04:07HP_Archivist (HP_Archivist) joins
18:40:52Ajay1 quits [Ping timeout: 250 seconds]
19:01:45HP_Archivist quits [Client Quit]
19:43:43nertzy_ joins
19:45:53nertzy__ quits [Ping timeout: 258 seconds]
19:52:20<rewby>If you just want to participate, I really think the warrior dockerfile is the best method. You'll automatically participate to any project in need
20:23:46spirit quits [Client Quit]
20:29:41<yano>a few days late, https://capslockday.org/
20:30:32<nyany>IT'S NEVER TOO LATE FOR THAT, YANO
20:30:39<nyany>HAPPY BELATED CAPS LOCK DAY
20:30:50<yano>HAPPY BELATED CAPS LOCK DAY
20:30:54<yano>TO YOU TOO
20:30:56<yano>lol
20:31:04<nyany><:
20:45:16<@JAA>WOW YANO, RUDE TO LAUGH SO LOUDLY!
20:52:40<yano>:O
21:09:12qwertyasdfuiopghjkl quits [Remote host closed the connection]
21:11:43qwertyasdfuiopghjkl joins
22:03:07Viniter6 quits [Quit: Ping timeout (120 seconds)]
22:05:58Viniter6 (Viniter) joins