-
Daniel
Link Mauve: very cool. Good job
-
Link Mauve
Hi, with the XSF infra, what would be the best way to run a script approximately once a day, with persistent cache and persistent artefacts exposed to the web?
-
Link Mauve
My current poc is a web app, but it could perfectly generate static files anyway.
-
Zash
Stuff it in Docker 🤷️
-
MattJ
Yes
-
Link Mauve
I have never done anything with Docker, but I’ll try to do that. :)
-
MattJ
Enjoy!
-
lskdjf
Link Mauve, nice work with the client/lib info alongside the xeps 🙂 One remark: I think it's not a great idea to try and squeeze all (or any, really) supporting client/server/lib logos into the XEP overview. For popular XEPs there are lots of supporting clients and servers (more than are currently included), and displaying each logo in the XEP-row requires a considerable amount of space. I'd suggest to either only display the supporting clients/servers/lib on the XEP page or at least to make it possible to show/hide them on the overview page and to hide them by default.
-
mathieui
yes, I think it would make sense to have it available but not displayed by default in the index (imo individual XEPs are fine though)
-
Link Mauve
lskdjf, indeed, that’s a good point.
-
Link Mauve
How would you do that, only pick a (random?) subset?
-
lskdjf
maybe I should clarify the brackets in my last sentence 😀 The hiding/not displaying was only about the overview page. Showing them in the XEP page is fine.
-
mathieui
Link Mauve, maybe showing the number instead of the list
-
mathieui
so it gives at least some information
-
mathieui
(I’m not an UX designer so don’t take my word too seriously though)
-
Link Mauve
I think I have something which looks like a working docker thingy now.
-
lskdjf
> How would you do that, only pick a (random?) subset? I don't think a random subset would be very helpful, as it doesn't really inform you about the popular xeps anymore (which is the main usecase of displaying it all, I guess?). I think hiding the full set of client/server logos from the overview by default would be a good idea. As an alternative I also like mathieui's suggestion of displaying the total number of implementations instead of individual logos, as it provides a sufficiently good (and short) overview.
-
emus
> lskdjf wrote: > Link Mauve, nice work with the client/lib info alongside the xeps 🙂 One remark: I think it's not a great idea to try and squeeze all (or any, really) supporting client/server/lib logos into the XEP overview. For popular XEPs there are lots of supporting clients and servers (more than are currently included), and displaying each logo in the XEP-row requires a considerable amount of space. I'd suggest to either only display the supporting clients/servers/lib on the XEP page or at least to make it possible to show/hide them on the overview page and to hide them by default. Maybe the client column could just link to a subpage with all clients supporting that XEP. Or a by default collapsed view Link Mauve:
-
lskdjf
> Maybe the client column could just link to a subpage with all clients supporting that XEP. the XEP page contains a table with all supporting clients already. I don't think it needs yet another page for that.
-
jonas’
lskdjf, does it?
-
jonas’
ah in that beta
-
lskdjf
jonas’, in Link Mauve's version, yes: https://linkmauve.fr/extensions/xep-0054.html
-
Link Mauve
Ok, 118G /var/lib/docker
-
Link Mauve
I mean, sure.
-
Link Mauve
Why not.
-
Link Mauve
I’ve played with it for a total of like one hour after all.
-
wurstsalat
one heavy whale
-
Link Mauve
It’s perfectly normal.
-
Link Mauve
This is fine.
-
mathieui
good thing you didn’t play with it using your toaster
-
jonas’
I don’t like✎ -
jonas’
I don’t like that particular rendering, but the idea is neat ✏
-
jonas’
Link Mauve, your counting is wrong
-
jonas’
there are a lot of mounted things, you need to run du with -x
-
jonas’
otherwise you’re counting the same things multiple times
-
Link Mauve
I rm -rf’d everything and started over.
-
jonas’
(re /var/lib/docker)
-
Link Mauve
I now have fiber, so I can waste that stuff. :p✎ -
Link Mauve
I now have fiber, so I can waste that bandwidth. :p ✏
-
Link Mauve
I now have fiber, so I can afford to waste that bandwidth. :p ✏
-
Link Mauve
Alright, my docker thingy works now.
-
Link Mauve
MattJ, Zash, feel free to clone https://git.linkmauve.fr/xmpp-doap.git, docker build xmpp-doap, and docker run -v ~/dev/web/xmpp.org:/xmpp.org -v ~/output/xmpp-doap:/data it. o/
-
Link Mauve
You’ll end up with the data in ~/output/xmpp-doap, put that directory at the root of https://xmpp.org and it will be ready.
-
MattJ
flow: smack is notably missing from✎ -
MattJ
flow: smack is notably missing from https://xmpp.org/software/libraries.html ✏
-
MattJ
Hmm
-
jonas’
Link Mauve, the root of xmpp.org lives in a docker container, not in a volume or somesuch
-
MattJ
"Put that data" step sounds ambiguous and tricky
-
jonas’
hm, so we’ll have to do a docker cp I think?
-
Link Mauve
Maybe?
-
jonas’
every time we update the xmpp.org thing
-
jonas’
sounds tricky
-
jonas’
maybe this should rather be a script inside the xmpp.org container which gets called by the entrypoint and which we can call as a cronjob from the host machine?
-
Link Mauve
I know nothing about docker, I just did one which generates the tree of files to be used.
-
Link Mauve
Couldn’t you also point the web server to that particular directory?
-
MattJ
That could work if it wasn't in the xmpp.org root
-
MattJ
/ goes to the xmpp.org container
-
jonas’
(where an nginx runs)
-
Link Mauve
What it needs is /xmpp-doap/ actually.
-
jonas’
and also the extensions/index.html?
-
Link Mauve
No, that’s /xmpp-doap/extensions.json
-
MattJ
jonas’: is nginx not outside the container? Or was that a different server?
-
jonas’
MattJ, both!
-
MattJ
Well, right
-
jonas’
there is an nginx on the host, and each web site part comes with its own nginx
-
jonas’
I love it /s
-
MattJ
So the host nginx can handle specific dirs
-
jonas’
Link Mauve, oh, so this requires JS to work?
-
jonas’
right
-
Link Mauve
jonas’, yes, I wanted to avoid to modify Pelican.
-
Link Mauve
It could be integrated possibly, but so far I’ve been unable to get it to build. ^^'
-
Zash
Is anyone on the website or iteam really familiar with Pelican?
-
jonas’
I am
-
jonas’
but not with the crude things which are done there
-
jonas’
the xmpp.org website is way beyond what pelican can easily do and it’s a crude hack
-
Zash
I think it would help the newsletter team a lot if they could preview the site easily, but that takes some major effort in my experience.
-
emus
Yes, it indeed would, but I only can do some python and lag any http or CSS stuff entirely 😬️