| 02:13:27 | | @arkiver quits [Excess Flood] |
| 02:13:59 | | arkiver (arkiver) joins |
| 02:13:59 | | @ChanServ sets mode: +o arkiver |
| 04:38:04 | | OrIdow6 quits [Quit: Quitting.] |
| 04:41:11 | | OrIdow6 (OrIdow6) joins |
| 05:20:14 | | s-crypt (s-crypt) joins |
| 06:17:11 | | @arkiver quits [Excess Flood] |
| 06:17:42 | | arkiver (arkiver) joins |
| 06:17:42 | | @ChanServ sets mode: +o arkiver |
| 11:26:04 | | Sylirana joins |
| 11:33:21 | <Sylirana> | Hey, I've been trying to run a warrior on a VPS using Docker, but it seems to be stuck at "The warrior is beginning work on a project.". Debug log: https://pastebin.com/raw/KDCp8PK2 . |
| 11:43:45 | <Sylirana> | Note: I am asking here instead of a project-specific channel since I've tried multiple projects and they all failed. |
| 14:58:59 | | bithippo joins |
| 14:59:00 | <@JAA> | Sylirana: Most projects (all except URLTeam I believe) currently won't run in the warrior. There's work ongoing to fix that though. |
| 18:13:08 | <OrIdow6> | FInally |
| 18:14:52 | <OrIdow6> | Sylirana: If you can run docker, you can run images from https://hub.docker.com/u/warcforceone , which should work |
| 18:15:43 | <OrIdow6> | Love that download counter thing... if only that many people were actually interested |
| 18:17:29 | <@JAA> | Yeah, the counters are grossly off due to watchtower. |
| 21:02:33 | <Sylirana> | After a lot of fiddling around, I managed to get the GitHub project to work inside some Frankenstein version of the warrior (My experience with both Python and Dockerfiles are pretty much 0.) and it runs fine now, but wget seems to follow *all* links and not just ones related to the repo. I just thought I happened to get a larger repo, so left it running, but both tasks are currently downloading some general GitHub information/help pages. At several |
| 21:02:33 | <Sylirana> | GB total now, while both repos combined are below 50 MB. I'll ask about that on the project-channel. When I have more time, I'll try to figure out exactly what things I did to get it running in the first place and document them, so maybe maintainers of the respective repos could hae a look. |
| 21:02:59 | <Sylirana> | *have |
| 21:21:18 | | Fusl (Fusl) joins |
| 21:21:18 | | @ChanServ sets mode: +o Fusl |
| 21:24:23 | | Sylirana quits [Read error: Connection reset by peer] |
| 21:24:35 | | Sylirana joins |
| 23:02:43 | <tech234a> | Fusl: (continuing the conversation from #gitgud) a test tracker would be nice, I was also starting to look through the Warrior code and had some ideas for making it use Docker containers (haven't implemented any of it yet so don't worry no invalid items :), and also I was planning on doing it in a way that wouldn't require modification of scripts at all) |
| 23:03:12 | <@Fusl> | tech234a: again, like written somewhere else, please dont waste brain cycles on this |
| 23:03:24 | <@Fusl> | you'd be implementing something that will be made obsolete when the new warrior is being released |
| 23:03:36 | <tech234a> | Ah where/when is that happening? |
| 23:03:42 | <@Fusl> | after the tracker rewrite |
| 23:04:07 | <@Fusl> | including the open tickets here: https://git.kiska.pw/ArchiveTeam/trackerproxy/issues |
| 23:05:10 | <tech234a> | Interesting... so I'm assuming this is a few months out? |
| 23:05:38 | <@Fusl> | 2-3 months |
| 23:07:03 | <tech234a> | Ah, well looking forward to it... thanks for letting me know before I wasted even more brain cycles on thinking this through :) |
| 23:11:41 | <@Fusl> | short too-long-dont-want-to-go-into-details explanation: there will be a central point where everyone can sign up and maintain their warrior infrastructure, control each single node, etc. |
| 23:15:48 | <tech234a> | FWIW my idea so far was to use the existing Warrior seesaw frontend (port 8001), but make selecting/deselecting a project start/stop a Docker container (port 8002, same HTTP auth credentials). It would use the docker python module. The websocket connected to in the interface on the main frontend (port 8001) would also have proxy for the messages incoming from the web UI on the Docker frontend (port 8002) for logs. Also AT project |
| 23:15:48 | <tech234a> | containers would be tagged for automatic updates from Watchtower. projects.json would have information on Docker images and the command used to initialize them. Like Watchtower, the AT port 8001 web config would be fed a Docker socket to manage, meaning it itself could also be a container outside of a VM. Seesaw itself would probably need a minor change: new CLI argument to put it in warrior mode so warrior icon appears on the tracker. |
| 23:15:48 | <tech234a> | Probably missing a lot of details that would need to be implemented but that where I was at. Anyway Fusl I'm sure your plan is a lot better :) |
| 23:23:48 | | Sylirana quits [Client Quit] |
| 23:38:10 | | Sylirana joins |