XSF Discussion - 2021-10-25

Is the registry not being kept up right now? I wondered if I could get a one off merge (and regen on the website) for https://github.com/xsf/registrar/pull/40

(trying to do codegen of some common configuration forms based on the registry but it's broken)

Sam: yes, the registry pipeline has been broken for a long time. I think help fixing it would be very welcome.

Sam: Its related to what page?

Sam: yes, registrar broken, someone needs to fix it, ideally not me

for bus factor and load reasons

I don't know that anyone has access to that except you, but if you're willing to give me access again I'd at least offer to try and fix it.

I guess anyone can do PRs

What does it even mean for the registrar to be working?

registry updates are checked and published

Oh, so I guess I don't understand the problem then, is it just reviewing and merging PRs that' the issue? If so sure, I volunteer to do that

Sam, no, merging stuff won't make anything happen to the website or so

no automated build, nothing

(I am aware of, anyway)

someone needs to do that

Oh, gotcha, yah, that's what I was volunteering to do initially

go ahead then please :). or point me at any PRs related to that, I've been ignoring the repository for most part because of its brokenness

I suspect that will need access as there's no dev environment for website deploys and we probably need to know how they work, but I'll look and see if I can guess enough of it to do a PR

Oh, or maybe there is, let me see what this DockerfileDev stuff is…

it would be a start to have a github actions thing or whatever which builds a docker image serving the registry in nginx

then all that needs to be done is to include it iteam-side

which should be easy enough

nginx container serving only https://xmpp.org/registrar/ ?

yes, like /xeps/

Sam, nothing in https://github.com/xsf/xmpp.org (i.e. DockerfileDev you mentioned) builds/has a connection to /registrar/. you'd have to start here: https://github.com/xsf/registrar

jonas’: https://github.com/xsf/registrar/pull/41

(I left off the actions part because I assume the iteam would prefer to build this however they do it for xmpp.org to keep things consistent, which is just a dockerhub thing IIRC)

Jabber.org is down.

Is it though?

I also can’t establish a s2s with it.

Neither with conference.jabber.org.

Ah no, only conference.jabber.org.

Dear folks, the end of the month is close. Please consider you chance to contribute your project news of this month to the newsletter! https://yopad.eu/p/xmpp-newsletter-365days 📝️

Link Mauve: MattJ says that there is no problem... - https://github.com/stpeter/jabberdotorg/issues/24

MattJ: I confirm the problem

I can too

https://downforeveryoneorjustme.com/jabber.org

It's just you

Maybe a peering issue ?

Some verification websites use https://www.jabber.org instead of https://jabber.org IPv4 is different: 185.199.110.153 (ok) VS 208.68.163.218 (down)

Nice uptime test: https://www.uptrends.com/tools/uptime

I don't exactly understand whats discussed here. But s2s is possible with jabber.org and the website works too, with and without www (its redirected to www)

The configuration is "special": http(s)://jabber.org has the IPv4 of an hosted server with main XMPP server + conference XMPP server + mailserver and the http(s)://www.jabber.org is another host.