@eyedeekay
&zzz
+R4SAS
+RN
+RN_
+Stormycloud
+acetone
+dr|z3d
+hagen
+mareki2p
+not_bob_afk
+orignal
+postman
+qend-irc2p
+snex
+weko
+wodencafe
AHOH2
Arch
BubbRubb
C341
Danny
DeltaOreo
FreefallHeavens
Irc2PGuest12542
Irc2PGuest43371
Irc2PGuest57893
Irc2PGuest82088
Irc2PGuest94314
Leopold
Onn4l7h
Onn4|7h
SigSegv
Sleepy
SlippyJoe
T3s|4_
Teeed
aargh
ardu
b3t4f4c3__
bak83_
cumlord
dr4wd3
eyedeekay_bnc
idontpee
ohThuku1
onon_
poriori
profetikla
r00tobo
rapidash
solidx66
thetia
u5657
uop23ip
w8rabbit
wew
x74a6
eyedeekay
Awesome happy to hear it, been busy reviving go-i2p and getting to website stuff but I'll be ready to at least respond on the day of
dr|z3d
still wrestling with gitlab, eyedeekay, or you've tamed it? :)
eyedeekay
gitlab's a constant struggle, you solve one thing and another pops up
eyedeekay
But for the most part
eyedeekay
There was a period there where they were doing a security release about once or twice a week, glad that's more-or-less over
dr|z3d
now I've found 'gitea doctor check' upgrading's a breeze.
eyedeekay
99% of the time the upgrade isn't too much of a problem anymore, last time it was it was gitlab's fault due to a faulty config migration script so we were on a dev build for about a week with the fix
dr|z3d
that's good, it's one less hassle if you can just pull the updates and restart the server without having to think too hard about it.
eyedeekay
There's a cronjob that runs every other day, usually nobody notices because it runs late at night
eyedeekay
Because gitlab takes about 7 or 8 minutes to reboot
dr|z3d
gitea, otoh, takes around 3s.
dr|z3d
apparently if you're super sensitive to licensing and ownership, forjego is the new gitea.
eyedeekay
Wild, forked again? I remember when it was gogs
dr|z3d
yeah, gitea got bought, some folk aren't happy, so forked but keeping synced with upstream.
eyedeekay
Good then they have my SAMv3 MR