#gitpages — Public Fediverse posts

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

With docker-ce rolled back to the previous version, everything now works, and I can deploy stuff to my internal pages server!

Because I use an internal Domain (wolkenheim.page) this is not even available through Tailscale properly yet, but it is progress.

Also, I will need to find a way to more easily deploy the SSL certificate for the wildcard domain than manual configuration using certbot. Since for wildcard domains part of the Challenge is DNS based, I am not yet sure how to do this.

#homelab #dns #forgejo #gitpages #tailscale #certbot #ssl #docker

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

With docker-ce rolled back to the previous version, everything now works, and I can deploy stuff to my internal pages server!

Because I use an internal Domain (wolkenheim.page) this is not even available through Tailscale properly yet, but it is progress.

Also, I will need to find a way to more easily deploy the SSL certificate for the wildcard domain than manual configuration using certbot. Since for wildcard domains part of the Challenge is DNS based, I am not yet sure how to do this.

#homelab #dns #forgejo #gitpages #tailscale #certbot #ssl #docker

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

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

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!

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/

#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 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!