01:53:18TheLovinator joins
02:50:37<tech234a>Are there specific specifications that need to exist for a Warrior implementation or is it just "run the projects effectively"?
07:44:02n9nes joins
08:51:56@arkiver quits [Excess Flood]
08:52:25arkiver (arkiver) joins
08:52:25@ChanServ sets mode: +o arkiver
13:25:36n9nes quits [Read error: Connection reset by peer]
19:19:45<OrIdow6>Why can't warrior-install.sh and wget-lua-warrior (mentioned on the wiki) be used to run the new wget-lua/wget-at versions?
19:24:28<@kiska>I think it can be run, you'
19:24:42<@kiska>you'll need to run the extra's project first then wget-at can be run
19:25:53<@JAA>Yeah, should work, but you need zstd 1.4.4 installed I think.
19:26:25<@kiska>I think the extra's project does that
19:26:30<@kiska>chfoo: ^
19:27:14<@JAA>Looks like it, yes: https://github.com/ArchiveTeam/warrior-extras-installer
19:31:20<@JAA>chfoo: The files in https://warriorhq.archiveteam.org/downloads/data/posterous/ are all 404.
19:32:35<@chfoo>the extras project installs it at /opt/wget-at-1.20.3/bin/wget-at so each warrior project needs to opt-in in finding it
19:33:49<@kiska>I guess an arkiver highlight is in order?
19:34:44<@chfoo>the posterous files are symlinks to /var/www/rsync/posterous-txt/ which i don't know what they are
19:35:13<@kiska>Was it a previous project which we don't know about?
19:36:05<@kiska>This sounds like something in this https://github.com/ArchiveTeam/posterous-grab
19:37:09<@JAA>They were already 404 three years ago, by the way: https://web.archive.org/web/20171014161743/https://warriorhq.archiveteam.org/downloads/data/posterous/2013-02-22-posterous-hostname-list.txt
19:40:22<@arkiver>i was highlighted
19:41:05<@arkiver>chfoo: thank, will use that
20:34:10<OrIdow6>Nice
20:35:38<OrIdow6>I assume this covers LuaSocket as well?
20:38:09<@kiska>I don't see it in the extra's repo but I think so?
20:46:24<@JAA>I don't see where it would. The warrior Dockerfile doesn't have it either.
20:46:37<@JAA>Speaking of which, the warrior VM still relies on the archiveteam/warrior-dockerfile Docker image which we can't update.
20:48:20<@kiska>I mean that can be easily installed right?
20:48:32<@kiska>In https://github.com/ArchiveTeam/warrior-extras-installer/blob/master/warrior-install.sh
20:49:46<@JAA>Might be messy since that doesn't run as root, so can't just do 'apt install lua-socket'.
20:49:56<@JAA>As I understand it, anyway.
20:50:37<@JAA>Ah, nevermind: https://github.com/ArchiveTeam/warrior-extras-installer/blob/3990c313b177b87d2dff7f306f40b12c284b0f30/install_zstd_x64.sh#L27
20:51:07<@JAA>Yeah, guess it should be added somewhere there.
20:51:41<@JAA>The grab-base Docker image also has libluajit-5.1-2, might be worth adding as well for performance, not sure.
20:51:47<@JAA>Why is Fusl not in here?
20:51:55<@kiska>Cause?
20:52:08<@JAA>Well, guess she doesn't care about the warrior anyway. :-P
20:52:12<@kiska>I thought wget-lua only worked on lua5.0?
20:52:36<@JAA>I've always been using 5.1.
20:53:17<@kiska>I see :D
20:53:35<@kiska>Would probably be a nice performance increase by going 5.1 then
20:54:15<@JAA>The warrior Docker image already has 5.1. Well, at least the Dockerfile does, no idea what's in the two-year-old unmaintained image on Docker Hub.
21:02:31<tech234a>It might just make sense to start fresh on the Warrior and just make it something that pulls and starts Docker containers from a list
21:02:45<tech234a>Containers for each project
21:03:46<tech234a>From a script development standpoint it would make sense because then only the Docker image has to be created and tested
21:04:36<@JAA>Yeah, that's the plan as far as I understood from discussion elsewhere recently.
21:05:36<tech234a>Has work started yet on this?
21:12:15<@arkiver>albumee project will have this
21:12:16<@arkiver>as test
21:16:32<@arkiver>actually no, need more testing for the Lua additions
22:25:01<@Kaz>docker img is now built