[00:06] ran rvm+rvm requirements in actual sudo account, then back to tracker user and everything else seems to work [00:06] now on to passenger... [00:33] broadcaster upstart conf: at least on my system it's called "nodejs", not "node" .. [00:38] error in starting broadcaster, apparently "The configure method has been removed from express as of version 4.0.0" [00:59] had to look in routes to find "global-admin" magic URL .. maybe because not accessing via 'localhost' host ? [01:01] the wiki may have typos. i believe you may be the first one to have read and followed it [01:03] wiki just says "visit http://localhost/" and jumps to to go Global Admin ... like there would be some direct link on first page [01:03] well, I have a tracker up and running.. sleep now and actually trying to use it tomorrow [10:20] Can I shove in a quick suggestion? For the tracker to be able to accept more responses back from warriors than a plain 'item done'. [10:21] (e.g. 'item refused' or 'error while downloading' so the tracker can know what's coming back, what needs re-allocating, etc) [10:22] (Likewise a small change to the pipeline so that 'Process WGetDownload WhateverItem' can post back an error to the tracker) [14:12] nickserv register moomoo twitter@services.dnt [14:14] whoops, ignore that. sorry, stuffed up a command in my client [14:43] https://github.com/ArchiveTeam/universal-tracker/issues/10 [17:02] Oh, nice [17:03] I still like the idea for the clients to be able to selectively 'refuse' items (e.g. if it's too big to be downloaded in a reasonable time on that user's connection, etc) using the same kind of mechanism [17:03] So they can bounce back to the tracker and be immediately allocated elsewhere [20:56] so "ArchiveTeam/example-seesaw-project" seemed like a good start.. but no send done to tracker [20:57] is send done to tracker even possible without rsync/others ? mainly how to properly construct stats object, maybe if there are no bytes