Link MauveHi, 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 MauveMy current poc is a web app, but it could perfectly generate static files anyway.
lovetoxhas joined
ZashStuff it in Docker 🤷️
MattJYes
intosihas joined
Link MauveI have never done anything with Docker, but I’ll try to do that. :)
MattJEnjoy!
Andrzejhas joined
lionelexecrechas left
lionelexecrechas joined
intosihas left
Andrzejhas left
Shellhas left
pasdesushihas joined
krauqhas left
krauqhas joined
intosihas joined
pasdesushihas left
chronosx88has left
chronosx88has joined
neshtaxmpphas left
pasdesushihas joined
intosihas left
moparisthebesthas joined
intosihas joined
marekhas joined
lionelexecrechas left
lionelexecrechas joined
Marandahas left
Marandahas joined
intosihas left
Marandahas left
Marandahas joined
Andrzejhas joined
lovetoxhas left
Marandahas left
krauqhas left
krauqhas joined
Marandahas joined
inkyhas joined
intosihas joined
krauqhas left
krauqhas joined
Marandahas left
Andrzejhas left
emushas left
intosihas left
emushas joined
Marandahas joined
debaclehas left
lskdjfLink 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.
debaclehas joined
mathieuiyes, I think it would make sense to have it available but not displayed by default in the index (imo individual XEPs are fine though)
werdanhas joined
Link Mauvelskdjf, indeed, that’s a good point.
Link MauveHow would you do that, only pick a (random?) subset?
lskdjfmaybe 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.
werdanhas left
mathieuiLink Mauve, maybe showing the number instead of the list
mathieuiso it gives at least some information
lovetoxhas joined
mathieui(I’m not an UX designer so don’t take my word too seriously though)
Link MauveI think I have something which looks like a working docker thingy now.
serge90has left
alameyohas left
intosihas joined
Andrzejhas joined
lionelexecrechas left
lionelexecrechas joined
lionelexecrechas left
lionelexecrechas joined
lionelexecrechas left
lionelexecrechas joined
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.
lionelexecrechas left
lionelexecrechas joined
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:
lionelexecrechas left
lionelexecrechas joined
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.
serge90has joined
jonas’lskdjf, does it?
intosihas left
jonas’ah in that beta
lskdjfjonas’, in Link Mauve's version, yes: https://linkmauve.fr/extensions/xep-0054.html
Link MauveOk, 118G /var/lib/docker
Link MauveI mean, sure.
Link MauveWhy not.
florettahas left
Link MauveI’ve played with it for a total of like one hour after all.
wurstsalatone heavy whale
Link MauveIt’s perfectly normal.
Link MauveThis is fine.
Sevehas left
mathieuigood thing you didn’t play with it using your toaster
jonas’I don’t like
lionelexecrechas left
lionelexecrechas joined
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 MauveI rm -rf’d everything and started over.
jonas’(re /var/lib/docker)
Link MauveI now have fiber, so I can waste that stuff. :p
Link MauveI now have fiber, so I can waste that bandwidth. :p
lovetoxhas left
Link MauveI now have fiber, so I can afford to waste that bandwidth. :p
Andrzejhas left
Link MauveAlright, my docker thingy works now.
lionelexecrechas left
lionelexecrechas joined
Link MauveMattJ, 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 MauveYou’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.
MattJflow: smack is notably missing from
MattJflow: smack is notably missing from https://xmpp.org/software/libraries.html
lionelexecrechas left
lionelexecrechas joined
MattJHmm
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 MauveMaybe?
jonas’every time we update the xmpp.org thing
lionelexecrechas left
lionelexecrechas joined
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 MauveI know nothing about docker, I just did one which generates the tree of files to be used.
Link MauveCouldn’t you also point the web server to that particular directory?
MattJThat could work if it wasn't in the xmpp.org root
eevvoorhas left
MattJ/ goes to the xmpp.org container
eevvoorhas joined
jonas’(where an nginx runs)
Link MauveWhat it needs is /xmpp-doap/ actually.
jonas’and also the extensions/index.html?
Link MauveNo, that’s /xmpp-doap/extensions.json
MattJjonas’: is nginx not outside the container? Or was that a different server?
jonas’MattJ, both!
MattJWell, right
jonas’there is an nginx on the host, and each web site part comes with its own nginx
jonas’I love it /s
MattJSo the host nginx can handle specific dirs
jonas’Link Mauve, oh, so this requires JS to work?
jonas’right
Link Mauvejonas’, yes, I wanted to avoid to modify Pelican.
Link MauveIt could be integrated possibly, but so far I’ve been unable to get it to build. ^^'
intosihas joined
lionelexecrechas left
lionelexecrechas joined
lionelexecrechas left
lionelexecrechas joined
alameyohas joined
ZashIs anyone on the website or iteam really familiar with Pelican?
lionelexecrechas left
lionelexecrechas joined
lionelexecrechas left
lionelexecrechas joined
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
alameyohas left
intosihas left
adiaholichas left
ZashI 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.
andrey.ghas left
pasdesushihas left
xeckshas left
xeckshas joined
lionelexecrechas left
lionelexecrechas joined
intosihas joined
lovetoxhas joined
lovetoxhas left
gavhas left
intosihas left
gavhas joined
lovetoxhas joined
Andrzejhas joined
Guushas joined
Andrzejhas left
lovetoxhas left
Guushas left
intosihas joined
florettahas joined
Sevehas joined
SnowCodehas joined
adiaholichas joined
fuanahas joined
wladmishas joined
lionelexecrechas left
lionelexecrechas joined
lionelexecrechas left
lionelexecrechas joined
intosihas left
Syndacehas left
Syndacehas joined
pasdesushihas joined
lionelexecrechas left
lionelexecrechas joined
pasdesushihas left
pasdesushihas joined
pasdesushihas left
pasdesushihas joined
pasdesushihas left
pasdesushihas joined
Andrzejhas joined
lionelexecrechas left
fuanahas left
lionelexecrechas joined
pasdesushihas left
pasdesushihas joined
pasdesushihas left
pasdesushihas joined
lionelexecrechas left
lionelexecrechas joined
lionelexecrechas left
lionelexecrechas joined
emusYes, it indeed would, but I only can do some python and lag any http or CSS stuff entirely 😬️