Login
You're viewing the functional.cafe public feed.

Replies

  • 💬 1🔄 0⭐ 0
  • Apr 24, 2026, 9:45 AM

    @whitequark Thank you! I will give it a try this evening. Really appreciate all of the work you and others are doing here and on ChiPass!

    💬 0🔄 0⭐ 1
  • Apr 25, 2026, 6:34 AM

    @whitequark I managed to rollback fine and then adjusted the publishing processes to use git-pages-cli locally to publish the rendered content rather than pushing to long-lived branches in git. That then allowed me to reupgrade the site to git-pages, and should hopefully also save storage costs for Codeberg since we will now be able to move from three distinct branches storing all of the content to just one (although I've noticed in the past that it seems like garbage collection never runs on the server side or something?). I may look into figuring out CI in the future to avoid the need for long-lived deploy tokens, but this works for now.

    I did run into one more issue after the second upgrade which was that some redirects stopped working, but I was able to find from reading the `git-pages` documentation that I just needed to add `!` after the http codes in the _redirects file to force using redirects over any existing route content, and it all started working as expected again.

    Thanks again for all of the effort that has gone into this and for the helpful advice

    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Apr 24, 2026, 9:42 AM

    @whitequark Yeah, totally understand the reasoning for not supporting git-lfs with git-pages. git-lfs certainly is a pain. I was just using it as I had assumed that it was the least burdensome on Codeberg infrastructure, but it is certainly possible that is an incorrect assumption on my part.

    💬 0🔄 0⭐ 0
  • Apr 24, 2026, 9:44 AM

    @westonsteimel I think that is probably true, but also you don't need direct git-lfs support; you could use a Forgejo Actions workflow (see the docs above) where you check out your submodules, LFS files, etc and then stuff them into pages

    💬 0🔄 0⭐ 0