[08:24] <SketchCow> Request from the Internet to run Warrior on VPS
[08:24] <SketchCow> Isn't that... what we have?
[09:36] <ersi> Yes, that's entirely possible
[17:40] <neverFORG> is warrior down?
[17:42] <antomatic> sadly, looks like it
[17:43] <neverFORG> yep
[17:43] <antomatic> ah, no, back up now
[17:43] <antomatic> LL Cool J with the triumphant comeback
[17:46] <Atluxity> tracker 502  bad gateway?
[17:46] <Atluxity> up now
[17:48] <neverFORG> wheres th floppy man?
[19:24] <Atluxity> what is seesaw-kit?
[19:26] <Atluxity> wre qt6 vb0,85% af transaktionsbeløbet
[19:27] <Atluxity> damn cat on keyboard
[19:27] <Atluxity> pasting my password like that
[19:33] <ersi> Atluxity: It's the python library/framework that we use
[19:33] <ersi> alard made it
[19:45] <Atluxity> its used only to make the pretty webface one get with a warrior or does it do more?
[19:48] <Atluxity> ah, the sesaw-kit has its own wiki
[19:54] <yipdw> Atluxity: the web interface is a part of seesaw
[19:58] <Atluxity> yes, I see it now
[19:58] <Atluxity> I'm writing a blog-post for some rather technical people and I just want to get stuff right
[19:59] <Atluxity> been looking at the code a bit and thing I have a fair understanding of the working now
[20:00] <ersi> It's for a little bit of everything, but basically it provides a pipeline, eventloop and a webserver
[20:01] <ersi> I think it's "best" to take a look at one of the projects pipelines to get a good grasp on what it can do
[20:03] <Atluxity> yeah, thats what I did
[20:03] <Atluxity> thanks
[20:03] <Atluxity> it seems like _the_ sentral part of a warrior
[20:05] <ersi> sure is
[20:05] <ersi> but there's some more
[20:05] <ersi> check out warrior-code2/ on https://github.com/ArchiveTeam/ as well
[20:18] <Coderjoe> warrior-code2 being the stuff the warrior vm uses to bootstrap the seesaw pipeline
[20:18] <Atluxity> ye
[20:19] <Coderjoe> i kinda want to make a cloud-warrior, which provides some of the warrior stuff, but with a central dashboard page so you can see all your warriors, what they're up to, and control them.
[20:20] <Coderjoe> but I don't know if I'll get around to that
[20:21] <ersi> Aren't there already a few AMIs with that?
[20:22] <Coderjoe> not that I'm aware of
[20:24] <Coderjoe> I suppose you could do something like that with puppet or the like
[20:31] <ersi> Uh.. Why even mix in puppet >_>
[20:31] <ersi> That'd be for scale
[20:34] <Coderjoe> ersi: and running 100+ ec2 instances isn't scale?
[20:35] <ersi> I didn't say so either
[20:36] <ersi> an AMI is practically just a template. The warrior is also practically just a template