I noticed that @Codeberg has static websites.
#commonLisp #lambdaMOO #softwareIndividuals #emacs
sharpsign priority-requestsp
I noticed that @Codeberg has static websites.
#commonLisp #lambdaMOO #softwareIndividuals #emacs
sharpsign priority-requestsp
There's an issue under heavy discussion at this moment as to whether #codeberg should continue with the pages service or not.
The server is apparently terribly broken and pages are unreliable.
https://codeberg.org/Codeberg-e.V./Discussion/issues/124#issuecomment-3923084
The only real eu option is to use statichost.eu instead.
https://www.statichost.eu/
It's a shame. It's one of the reasons that I recently moved to codeberg. I checked the doc, it said it worked, but then to use CI you need to get approved for the purpose as resources are limited.
But really, you probably shouldn't use codeberg pages, even for your #jekyll site.
I had to be logged in to codeberg to see it.
Im also a supporter. I don't know if that makes a difference. I also didn't sign up to follow that issue.
It just started showing up in my mailbox. It's been going steadily for days. It doesn't look like there's a resolution. Pages is unreliable.
I agree. I like #codeberg a lot. I donate.
They have limited resources and the pages server is overwhelmed.
As I started to put pages in to use the doc was slightly discouraging. But one of the main arguments is to turn it off, or at least state its unreliablity up front. I am ready to turn it on. But I'm not going to now.
I'm going to try #statichost and use codeberg for my repos. It doesn't hurt me.
For big projects in need of a site, this seems to be problematic. GitHub and gitlab have spoiled people and raised expectations.
My site is certainly not a stress, and even the potential downtime is not a problem. I think the CI
Is also being taxed.
I don't need to be a pioneer or add to the weight that is already there. Tildeverse is interesting, you do have to use their git. Static host will pull your site from wherever it is. So I can leave it in codeberg.