#gitpages — Public Fediverse posts

RE: https://mastodon.wolkenheim.eu/@Wolkensteine/116795057265112295

I'm now also working on a way to reliably integrate git-pages into my Home Lab. I am just missing an automated way of getting wildcard certificates from my local CA!

Since I don't know much of the technical details of ACME I decided that I wouldn't search for a ready-made tool to solve this problem, but build one myself, fully according to RFC3555.
I am not yet sold on making that open, since I will surely make some huge mistakes, but if others are interested in a tool to have DNS-01 challenges solved with a PiHole DNS provider I might open source the project when I am done with the basics and feel comfortable with it.

#coding #programming #rust #forgejo #gitpages #selfhosting #dns #acme #homelab #selfsignedcerts #certificateauthority

RE: https://mastodon.wolkenheim.eu/@Wolkensteine/116795057265112295

I'm now also working on a way to reliably integrate git-pages into my Home Lab. I am just missing an automated way of getting wildcard certificates from my local CA!

Since I don't know much of the technical details of ACME I decided that I wouldn't search for a ready-made tool to solve this problem, but build one myself, fully according to RFC3555.
I am not yet sold on making that open, since I will surely make some huge mistakes, but if others are interested in a tool to have DNS-01 challenges solved with a PiHole DNS provider I might open source the project when I am done with the basics and feel comfortable with it.

#coding #programming #rust #forgejo #gitpages #selfhosting #dns #acme #homelab #selfsignedcerts #certificateauthority

So, if folks are using git-pages to deploy their static websites (e.g. via the *new* Codeberg Pages) and are building with the Woodpecker CI, I made this small plugin for pushing the build pages out:

https://codeberg.org/gedankenstuecke/git-pages-woodpecker-plugin

#codeberg #gitpages #woodpeckerci #opensource

Progress on the #selfhosted side of things combined with my #did / #dut work: Forgejo for the content, git-pages to serve and MyCI to build and publish 🎉

I gave git-pages a small reverse proxy in front of it, so that publishing is only possible from the local network.

#forgejo #gitpages #myci

Progress on the #selfhosted side of things combined with my #did / #dut work: Forgejo for the content, git-pages to serve and MyCI to build and publish 🎉

I gave git-pages a small reverse proxy in front of it, so that publishing is only possible from the local network.

#forgejo #gitpages #myci

FestivalGuide now has its own domain with a little static page hosted by @Codeberg
Do you like it?

https://festivalgui.de/

#staticpages #gitpages #codebergpages

My new website for work is a bit too minimalistic. It is served via git-pages though 😃

#gitpages

Got git-pages set up in my Kubernetes cluster finally. Using it with my local Forgejo with a wildcard domain and also to host a few static websites.

Working out the configuration was ok, some details slightly tricky. The configuration needs are small though, so I think this is manageable.

Have to get used to the DNS based auth for custom domains though.

https://git-pages.org, #selfhosted, #gitpages, #forgejo

Got git-pages set up in my Kubernetes cluster finally. Using it with my local Forgejo with a wildcard domain and also to host a few static websites.

Working out the configuration was ok, some details slightly tricky. The configuration needs are small though, so I think this is manageable.

Have to get used to the DNS based auth for custom domains though.

https://git-pages.org, #selfhosted, #gitpages, #forgejo

if you have questions about using or deploying #GitPages there is now an IRC channel #git-pages on libera.chat, and also a Matrix room #git-pages:catircservices.org!

if you have questions about using or deploying #GitPages there is now an IRC channel #git-pages on libera.chat, and also a Matrix room #git-pages:catircservices.org!

RE: https://social.treehouse.systems/@whitequark/116454915873481567

Anyone publishing a Quarto blog with Codeberg Pages? I'm new to this automation stuff, and can't decide between WebHooks, Forgejo Actions, and WoodPecker CI. If I use actions or WoodPecker, it would be just for "quarto render"; any R code output is frozen and will be run on my own computer. I have a custom domain.

#QuartoPub #CodebergPages #GitPages #ForgejoActions #WoodPeckerCI

RE: https://social.treehouse.systems/@whitequark/116454915873481567

Anyone publishing a Quarto blog with Codeberg Pages? I'm new to this automation stuff, and can't decide between WebHooks, Forgejo Actions, and WoodPecker CI. If I use actions or WoodPecker, it would be just for "quarto render"; any R code output is frozen and will be run on my own computer. I have a custom domain.

#QuartoPub #CodebergPages #GitPages #ForgejoActions #WoodPeckerCI

@Codeberg now provides a #gitpages instance that can be used to deploy your website.

I already moved my main blog to it and will eventually move other things too...

I also made a blog post that explains how you can deploy using the @forgejo Action workflow for it:

https://andre601.ch/blog/2026/04-24-using-git-pages-on-codeberg/

@Codeberg now provides a #gitpages instance that can be used to deploy your website.

I already moved my main blog to it and will eventually move other things too...

I also made a blog post that explains how you can deploy using the @forgejo Action workflow for it:

https://andre601.ch/blog/2026/04-24-using-git-pages-on-codeberg/

#GitPages now has a _redirects file linter that warns you if your redirect accidentally ends up "dead" (never triggered because you have a file with the same name)

#GitPages now has a _redirects file linter that warns you if your redirect accidentally ends up "dead" (never triggered because you have a file with the same name)

#GitPages now supports incremental site updates when uploading via the CLI!

pictured are logs for two individual uploads:
1a. PUT probe (says blobs are missing)
1b. PUT upload (uploads all the blobs)
2. PUT probe (says all the blobs are already there)

#GitPages now implements an audit system that allows on-line, background processing of uploaded content to e.g. scan it for viruses, phishing, and other abusive material

I consider this table stakes for any service with open registration, so now I can finally say that git-pages is _almost_ done (it needs a GC and a few minor fixes to other functions)

https://codeberg.org/git-pages/git-pages/issues/82#issuecomment-8707941

#GitPages now implements an audit system that allows on-line, background processing of uploaded content to e.g. scan it for viruses, phishing, and other abusive material

I consider this table stakes for any service with open registration, so now I can finally say that git-pages is _almost_ done (it needs a GC and a few minor fixes to other functions)

https://codeberg.org/git-pages/git-pages/issues/82#issuecomment-8707941

#GitPages now supports atomic partial updates using the PATCH method: give it a subdirectory and it will update its contents without touching anything else

you can use it to e.g. upload previews of built documentation without having to maintain giant git checkouts with stale files for thousands of pull requests. and it's efficient, too!

see https://codeberg.org/whitequark/whitequark.codeberg.page/src/commit/fc1c39ab1bfdd934934551de5ed9b7792f9d1d22/.forgejo/workflows/publish.yaml for an example workflow

https://whitequark.codeberg.page/
https://whitequark.codeberg.page/preview/pull/1/

#GitPages now supports atomic partial updates using the PATCH method: give it a subdirectory and it will update its contents without touching anything else

you can use it to e.g. upload previews of built documentation without having to maintain giant git checkouts with stale files for thousands of pull requests. and it's efficient, too!

see https://codeberg.org/whitequark/whitequark.codeberg.page/src/commit/fc1c39ab1bfdd934934551de5ed9b7792f9d1d22/.forgejo/workflows/publish.yaml for an example workflow

https://whitequark.codeberg.page/
https://whitequark.codeberg.page/preview/pull/1/

check out how quickly #GitPages (and #Grebedoc) can check out a giant git repository without any changes!

if supported by the server, it retrieves only a single tree from git (no other branches, no tags, no history, no file contents), backfills it from the existing site contents, and then pulls in any missing files from the git server on-demand

this lets you publish very large repositories as static sites without straining network and compute (for compression, etc) resources!

check out how quickly #GitPages (and #Grebedoc) can check out a giant git repository without any changes!

if supported by the server, it retrieves only a single tree from git (no other branches, no tags, no history, no file contents), backfills it from the existing site contents, and then pulls in any missing files from the git server on-demand

this lets you publish very large repositories as static sites without straining network and compute (for compression, etc) resources!