| Time |
Nickname |
Message |
|
08:26
🔗
|
soultcer |
alard. I think I broke the warriorhq |
|
09:26
🔗
|
GLaDOS |
soultcer: the trackers are broked as well. |
|
09:27
🔗
|
soultcer |
Oh, then it might not have been me |
|
09:27
🔗
|
soultcer |
We had the problem before that the tracker used too much memory |
|
09:28
🔗
|
soultcer |
The tracker uses redis as database which keeps everything in ram |
|
09:28
🔗
|
omf_ |
If punchfork is done we could take that down |
|
09:28
🔗
|
soultcer |
Anyone besides chronomex and alard have access to the tracker server? |
|
15:33
🔗
|
ersi |
soultcer: If I'm not mistaken, the "tornado" python library also needs to be compiled (regarding earlier conversation) |
|
15:56
🔗
|
soultcer |
thx |
|
21:17
🔗
|
soultcer |
alard: Would adding http basic auth to the warrior as a simple configuration option in the config.json file be ok? |
|
21:18
🔗
|
alard |
soultcer: I don't have objections to http basic auth. But config.json? |
|
21:18
🔗
|
soultcer |
Well, all config stuff for seesaw is stored in there |
|
21:19
🔗
|
soultcer |
And I made the ec2 image read the "userdata" and put it into config.json |
|
21:19
🔗
|
alard |
In that case it's probably a file that gets overwritten. |
|
21:20
🔗
|
alard |
But looking at the code I think it's saving everything, including new config values, so that should be okay. |
|
21:21
🔗
|
alard |
You could even add it as an option in the configuration panel: https://github.com/ArchiveTeam/seesaw-kit/blob/master/seesaw/warrior.py#L146-L172 |
|
21:21
🔗
|
soultcer |
If I make two ConfigValues "http_auth_user" and "http_auth_password", it should work fine, right? |
|
21:21
🔗
|
alard |
Yes. |
|
21:22
🔗
|
soultcer |
And then in seesaw/web.py I simply do a check if there is http auth set, and enforce it if it is |
|
21:22
🔗
|
alard |
Yes. Do you know how that works with the websocket connection? |
|
21:23
🔗
|
soultcer |
I have no idea but I guess I will have to learn it :D |