[00:11] *** ete_ has quit IRC (Read error: Connection reset by peer) [00:11] *** cechk01 has quit IRC (Read error: Connection reset by peer) [00:59] *** sep332 has quit IRC (Read error: Operation timed out) [01:00] *** sep332 has joined #warrior [01:02] *** bwn has quit IRC (Read error: Connection reset by peer) [01:03] *** bwn has joined #warrior [01:43] *** bwn_ has joined #warrior [01:49] *** bwn has quit IRC (Read error: Operation timed out) [01:59] *** JesseW has joined #warrior [02:26] *** Start has joined #warrior [03:10] *** cechk01 has joined #warrior [03:38] *** Start has quit IRC (Quit: Disconnected.) [03:40] *** bwn_ has quit IRC (Read error: Operation timed out) [03:40] *** Start has joined #warrior [03:52] *** balrog has quit IRC (Bye) [03:54] *** balrog has joined #warrior [03:54] *** swebb sets mode: +o balrog [04:10] *** JetBalsa has joined #warrior [04:11] Still would be nice to have a script that can make a debian system into a nice warrior without breaking the existing system [04:19] You mean something to install virtualbox and automatically import and start the Warrior? Or to automatically run new projects as they occur? [04:21] run new projects as they occur [04:21] while not being in a virtual machine (pretty much I want to run it on hardware that does not support VM Tech) [04:22] like if I wanted to donate a VPS to the cause [04:23] there is a docker container, but what if I wanted to donate some vps and set / forget [04:23] might help make it more widespread with people [04:24] I might start digging into how the warrirors are made and making the build scripts needed to make things flow right [04:30] https://github.com/ArchiveTeam/warrior-code2 [04:30] dat datadisk [04:30] ya I am looking it over now [04:33] shoving it all into a virtualenv [04:38] well [04:38] THAT was easy [04:38] lets try a project [04:38] virtualenv FTW [04:49] whoops found a bug [04:49] in the yuko wget-lua [05:04] *** JetBalsa has quit IRC (Quit: Page closed) [05:04] set/forget is nice for some running it and a pain in the ass to manage at scale [05:05] next time someone gets overambituous dreams of automation, let them know that [05:05] by "manage" I mean for the project admin, who has to figure out which subset of misbehaving systems to ban [05:06] it usually causes no trouble for the person running a gazillion VPSes because they probably forgot about half of them [05:07] *** aaaaaaaaa has quit IRC (Leaving) [05:37] *** JetBalsa has joined #warrior [05:43] *** nertzy has joined #warrior [06:17] *** nertzy has quit IRC (Quit: This computer has gone to sleep) [07:51] *** bwn_ has joined #warrior [07:57] *** JesseW has quit IRC (Leaving.) [08:45] *** midas1 is now known as midas [08:59] *** JetBalsa has quit IRC (Read error: Connection reset by peer) [14:42] *** nertzy has joined #warrior [15:27] *** nertzy has quit IRC (Quit: This computer has gone to sleep) [18:19] *** nertzy has joined #warrior [19:03] *** nertzy has quit IRC (Quit: This computer has gone to sleep) [19:11] *** bwn_ has quit IRC (Read error: Operation timed out) [19:25] *** aaaaaaaaa has joined #warrior [19:28] *** xmc has quit IRC (Quit: brb rebooting) [19:40] *** bwn has joined #warrior [19:42] *** xmc has joined #warrior [19:42] *** swebb sets mode: +o xmc [21:01] *** JetBalsa has joined #warrior [23:32] *** dvd has joined #warrior [23:48] *** dvd has quit IRC () [23:48] *** dvd has joined #warrior [23:53] *** dvd has quit IRC (Client Quit) [23:53] *** dvd has joined #warrior [23:56] *** dvd has quit IRC (Client Quit) [23:56] *** dvd has joined #warrior [23:59] *** dvd has quit IRC (Client Quit)