<whitequark>
i guess guard defaults to off nowadays?
whitequark[cis] has joined #git-pages
<whitequark[cis]>
test
<whitequark>
yay
<crystal>
yeah I think guard has always defaulted to off on liberachat, iirc it was changed on Freenode many years ago
<whitequark>
ah til
<whitequark>
mm someone should add the links to the rooms in all the READMEs
dpk has joined #git-pages
<whitequark>
maybe as one of those "badge" images? they're attention-grabbing, which in case of CI (that ought to always be green) is kinda useless but for support channels is actually good
<dpk>
pfft, you’ll never convince me that whitequark[cis] is cis
<whitequark>
it's originally a contraction of catircservices, like [m]
<crystal[m]>
Do you want the matrix bridge added to the projects on codeberg space?
<crystal[m]>
Or should it be under the main codeberg space?
<whitequark[cis]>
oh
<whitequark[cis]>
I'm not sure
<whitequark[cis]>
I had realized after you asked that I totally misremembered how Matrix spaces worked
<whitequark[cis]>
probably the main one seeing as it's a core part of a service Codeberg offers
<whitequark[cis]>
but it's not a strong opinion
<whitequark[cis]>
it's both in codeberg and on codeberg
<crystal[m]>
well, yeah, that's why I wasn't entirely sure, I assume this channel is for the project itself, which is _on_ codeberg, but I imagine people will also use this room for support on _new_ codeberg pages, which is part of codeberg
gusted[m] has joined #git-pages
<gusted[m]>
I suppose #gitea-pages-server:matrix.org will be repurposed to be pages@codeberg which is just git-pages and codeberg-pages-server.
<whitequark[cis]>
I don't have clear answers to any of this tbqh
<whitequark[cis]>
I don't mind having people come to this channel for support with Codeberg specifically
<whitequark[cis]>
it seems less frustrating to end users than coming to the "wrong" channel and not getting an answer quickly because someone who could answer it was in another one
<whitequark[cis]>
but I suppose this is already somewhat the case now that there are two channels (of course, the project did need its own)
<crystal[m]>
gusted[m]: I guess the real question is if that channel should evolve to become the main support channel for codeberg pages as the old pages-server is gradually phased out or if the channel itself should be deprecated and remain for the old pages server while this one carries forward support for the new server.
<crystal[m]>
Honestly I think it's a distinction that a lot of end users will not understand anyway so we'll probably be servicing requests in both channels no matter what
<gusted[m]>
Honestly, it was never used to support the old pages server, just "pages at codeberg"
<whitequark[cis]>
this is why I'm thinking that going with the latter option will eventually produce a desired end result where the end users don't have to flip a coin
<crystal[m]>
I know that, but at some point someone who was in charge of the project decided that the channel should be branded as "gitea pages server" which is extremely misleading
<whitequark[cis]>
(there is a consideration of the possibility of the codeberg-specific support requests being overwhelming, but I think this is very unlikely: first, git-pages is inextricably linked to codeberg anyway; second, the support load it created so far has been extremely low and even lower than anticipated; third, if it becomes that frustrating to use we should just fix it so that it's not)
<crystal[m]>
I guess I'll just add this to the codeberg root space for now and we can move it down to projects later if we decide that's more appropriate
<whitequark>
sgtm
<dpk>
speaking of Codeberg Pages, it’s down or else very slow
<whitequark[cis]>
(1 hour from channel creation to an off-topic message, must be some kind of record)
<dpk>
i aim to please
<whitequark[cis]>
i've felt for a while that "Static pages made easy" byline on a service that goes down multiple times daily sometimes reads a bit, how do I put it
<dpk>
:D
<whitequark[cis]>
... there's a clear gap between desire and reality, let's put it that way
<dpk>
apparently it’s just the old pages server which is down, git-pages is still working
<binwoes>
meow
<dpk>
so we should probably migrate codeberg.page to git-pages now …
<whitequark>
that would seem to be the thing to do
<gusted[m]>
Let's keep Codeberg specifics strictly in Codeberg channels, otherwise more channels to monitor 😵💫
<whitequark>
ack
<dpk>
i also alerted the relevant beings in the relevant location, don’t worry ;-)
<avioletheart>
binwoes, meow
<dpk>
okay, https://codeberg.page itself is now served by git-pages instead of through the legacy pages server :-)
<dpk>
incidentally if there’s a better way to force it to switch over (or otherwise send a webhook for an otherwise unchanged site) without `git commit --allow-empty` and then pushing that empty commit, i’d be glad to know it …