zzz
eyedeekay, eche|on, primary news server still down, reported weeks ago? you should fix before release
eyedeekay
I thought I had it back up will look again
zzz
thanks. don't know, tried a couple times
zzz
if the reliability cannot be assured long-term, we need to discuss other solutions
eche|off
last time I got reported I started it
eche|off
did anyone stopped it? any new release or alike?
zzz
it's returning 503 i2pnews.i2p
zzz
so router is fine
eche|off
last logentry 4th dec
eche|off
bah, pyython2 aspp
eche|off
[18/Dec/2023 14:07:22] "GET /news.su3 HTTP/1.1" 200
eche|off
should run again
eche|off
never touched it, whatever was wrong with it
eche|off
but as its still python2, need upgrade to python3 as the website does, to
zzz
eyedeekay, can you add it to your monitoring system that I think you have?
zzz
shouldn't be me that keeps discovering it's down
zzz
this is "critical infrastructure"
eche|off
from a securioty PoV that server should be offline, as python2 is out of support and we cannot upgrade, but as no one can do a new website now, it is still online
eche|off
samen with the flask news server
zzz
that's for you guys to fix then
zzz
please discuss at CCC how to work through this backlog of problems: news, website, email gateway, ...
zzz
we also need a hostname for the new repo ASAP
eche|off
I need someone doing the python stuff, I cannot do that and in last resort I will shut down thge website
eche|off
as I cannot do other way
eche|off
lets see what we can discuss on ccc
eche|off
the DNS for the deb repo came to me, need to enter if I find the time slot
eche|off
ok, currently servcer maintenanceat hetzner
eche|off
no dns entry today
dr|z3d
git.i2p.net no?
eyedeekay
we're talking about deb.i2pgit.org/deb.i2p.net
eyedeekay
regarding i2p.newsxml, it will run on python3 fine, has for a couple years, but the chart that's presented at the root of the primary server doesn't
dr|z3d
ah yeah, my bad.
eyedeekay
There's also the Go port of i2p.newsxml I could switch us over to
eyedeekay
Mine stays up for a couple reasons: 1) no python involved in the deployment, I just drop the static files in lighttpd's docroot, and 2) lighttpd is supervised so if lighttpd stops it gets restarted immediately
eyedeekay
official deadline for translations is in about 80 minutes which is when I'm going to `git tag i2p-2.4.0`