#warrior 2020-01-10,Fri

↑back Search

Time Nickname Message
00:16 πŸ”— second has quit IRC (Quit: ZNC 1.6.5 - http://znc.in)
00:23 πŸ”— second has joined #warrior
01:56 πŸ”— Flashfire has quit IRC (Remote host closed the connection)
01:56 πŸ”— kiska has quit IRC (Remote host closed the connection)
01:57 πŸ”— Flashfire has joined #warrior
01:57 πŸ”— kiska has joined #warrior
03:22 πŸ”— ivan has quit IRC (Quit: Leaving)
03:23 πŸ”— ivan has joined #warrior
03:34 πŸ”— ivan_ has joined #warrior
03:36 πŸ”— ivan has quit IRC (Ping timeout: 745 seconds)
05:24 πŸ”— ivan_ is now known as ivan
08:31 πŸ”— oshura has quit IRC (Read error: Connection reset by peer)
10:24 πŸ”— Smiley has joined #warrior
11:22 πŸ”— prq has quit IRC (Remote host closed the connection)
12:08 πŸ”— mtntmnky has quit IRC (Remote host closed the connection)
12:08 πŸ”— mtntmnky has joined #warrior
12:58 πŸ”— prq has joined #warrior
16:09 πŸ”— nyany Is there any way to pass variables like the nickname or the concurrency to the warrior when starting the docker image for the first time?
16:11 πŸ”— atphoenix not that I know of, but I'm not a SME. I do know you have set both parameters in the warrior web UI. Concurrency max=6 in web ui
16:12 πŸ”— nyany Ah, okay.
16:12 πŸ”— atphoenix presumably you *could* write something that calls the webUI and sets those params there
16:12 πŸ”— nyany I've got a working stackscript to deploy it on Linode, is why I'm asking
16:14 πŸ”— atphoenix I've only used the Warrior Virtualbox VM version (which has docker inside), not the separate docker version.
16:17 πŸ”— nyany heh, there IS
16:18 πŸ”— nyany I'm going to give it a go!
16:23 πŸ”— Kaz yes, you just set the vars when you run it
16:25 πŸ”— nyany yeah, I've noticed
16:37 πŸ”— atphoenix has quit IRC (Ping timeout: 276 seconds)
16:38 πŸ”— DogsRNice has joined #warrior
16:40 πŸ”— atphoenix has joined #warrior
16:45 πŸ”— atphoenix has quit IRC (Client Quit)
16:45 πŸ”— atphoenix has joined #warrior
16:46 πŸ”— atphoenix has quit IRC (Read error: Connection reset by peer)
16:46 πŸ”— atphoenix has joined #warrior
16:48 πŸ”— prq nyanyβ–Έ the docker image does look at variables. one moment.
16:48 πŸ”— nyany prq: yeah, I found the documentation, I'll play around with it in a bit
16:49 πŸ”— prq https://github.com/ArchiveTeam/warrior-dockerfile#using-environment-variables
16:49 πŸ”— nyany everything I need to know is... yeah
16:49 πŸ”— nyany there
16:49 πŸ”— prq for what it's worth, I found that CONCURRENT_ITEMS seems to be ignored and it uses the default 2.
16:49 πŸ”— nyany ah
16:49 πŸ”— nyany since you're here, could I bother you to have a quick look at this...
16:50 πŸ”— prq sure
16:50 πŸ”— nyany https://www.irccloud.com/pastebin/pWdpVf6g/
16:50 πŸ”— nyany This doesn't seem to work properly
16:51 πŸ”— prq get rid of the extraneous -e arguments
16:51 πŸ”— prq oh I must have had a typo last time I tried CONCURRENT_ITEMS
16:53 πŸ”— nyany Do I leave the one at the top?
16:54 πŸ”— nyany as per the documentation the first line has an extra -e
16:54 πŸ”— prq where in the documentation are you looking?
16:55 πŸ”— prq docker run --help has some info that's helpful here. --env and -e are aliases. if you specify --env/-e then the next thing needs to be a key/value. doing '--env FOO=bar -e --env BING=baz' doesn't make sense.
16:56 πŸ”— prq '-e FOO=bar -e BING=baz' does and is equivalent to '--env FOO=bar --env BING-baz' but that extra -e in your pastebin is a typo (even if you copied it from somewhere)
16:57 πŸ”— prq ah I found where the typo came from: https://hub.docker.com/r/archiveteam/warrior-dockerfile/
16:57 πŸ”— prq I don't know who has access to that Docker Hub account, but they'd need to log in and edit the doc that way.
16:58 πŸ”— nyany so it's not necessary
16:58 πŸ”— nyany perfect
17:04 πŸ”— nyany neat, it works prq
17:58 πŸ”— Wingy has quit IRC (The Lounge - https://thelounge.chat)
18:01 πŸ”— Wingy has joined #warrior
18:41 πŸ”— nyany I'm going to touch up the script but it seems stupid easy. I'll publish it to the community stackscripts so everyone else can run the warrior easily on Linode
18:52 πŸ”— Wingy has quit IRC (The Lounge - https://thelounge.chat)
18:53 πŸ”— Wingy has joined #warrior
20:57 πŸ”— mtntmnky has quit IRC (Read error: Operation timed out)
21:21 πŸ”— Atom has quit IRC (Read error: Operation timed out)
22:23 πŸ”— Atom has joined #warrior
22:35 πŸ”— Atom has quit IRC (Ping timeout: 276 seconds)
22:40 πŸ”— Atom has joined #warrior
22:44 πŸ”— Decobus has quit IRC (https://quassel-irc.org - Chat comfortably. Anywhere.)
23:29 πŸ”— Decobus has joined #warrior

irclogger-viewer