home.social

#codebergpages — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #codebergpages, aggregated by home.social.

fetched live
  1. Hey #CodebergPages users. I was wondering if user pages endpoints were also under Anubis protection.

    I know the docs git-pages docs are still in the works and everything, so I figured I'd ask here.

    @Codeberg

  2. Hey #CodebergPages users. I was wondering if user pages endpoints were also under Anubis protection.

    I know the docs git-pages docs are still in the works and everything, so I figured I'd ask here.

    @Codeberg

  3. One more step towards EU tech! 🇪🇺
    I've moved my site from GitHub Pages to Codeberg Pages.
    All processes and parts – writing, building, and hosting are now in the EU 💻

    #eutech #EUAlternatives #codeberg #codebergpages

  4. One more step towards EU tech! 🇪🇺
    I've moved my site from GitHub Pages to Codeberg Pages.
    All processes and parts – writing, building, and hosting are now in the EU 💻

    #eutech #EUAlternatives #codeberg #codebergpages

  5. RE: social.treehouse.systems/@whit

    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

  6. RE: social.treehouse.systems/@whit

    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

  7. At long long last, my blog is up and running!

    thelastpsion.com

    I'll be bringing all of my old hackaday.io posts over as soon as I can, with some updates and annotations.

    It'll mostly be about my #Psion adventures, but I'll also be posting information about the myriad sidequests I'll be going on.

    Thanks to #CodebergPages for hosting it, along with psion.community.

  8. At long long last, my blog is up and running!

    thelastpsion.com

    I'll be bringing all of my old hackaday.io posts over as soon as I can, with some updates and annotations.

    It'll mostly be about my #Psion adventures, but I'll also be posting information about the myriad sidequests I'll be going on.

    Thanks to #CodebergPages for hosting it, along with psion.community.

  9. I wrote a step-by-step guide on how to host your #gohugoio based website on #codeberg pages with the help of #forgejo actions:

    codeberg.org/steiger/hugo-on-c

    The setup does not yet support custom domains. I will update the documentation, as soon as this is supported.

    #codebergpages #diday #did

  10. I wrote a step-by-step guide on how to host your #gohugoio based website on #codeberg pages with the help of #forgejo actions:

    codeberg.org/steiger/hugo-on-c

    The setup does not yet support custom domains. I will update the documentation, as soon as this is supported.

    #codebergpages #diday #did

  11. If you're interested in the changes behind the scenes, Ive added some basic notes here around using Codeberg pages and Zola: fluids.rocks/posts/how-this-si #zola #codebergpages #blog

  12. Working on moving and perhaps resurrecting what *almost* became a blog a decade back. Changed tooling, made it a little simpler and hopefully a little more accessible, and it's now on Codeberg. Hoping to get a few useful snippets, guides etc onto a page, where I'm able to. These days posts will be more likely to cover spatial and spectral data analysis/software, Python and occasional self-hosting notes than what once would have been geochemistry and geology.

    Will live at: fluids.rocks [edit: updated domain] #codebergpages #blog

  13. Working on moving and perhaps resurrecting what *almost* became a blog a decade back. Changed tooling, made it a little simpler and hopefully a little more accessible, and it's now on Codeberg. Hoping to get a few useful snippets, guides etc onto a page, where I'm able to. These days posts will be more likely to cover spatial and spectral data analysis/software, Python and occasional self-hosting notes than what once would have been geochemistry and geology.

    Will live at: fluids.rocks [edit: updated domain] #codebergpages #blog

  14. @fredonline And the funny part, the IP for #codeberg pages seems to have been changed as well! That was the reason, that both my static sites were down. Fixed them in the DNS records to get them back up and running. I guess I missed their announcement for the change in IP. #codebergpages

  15. @fredonline And the funny part, the IP for #codeberg pages seems to have been changed as well! That was the reason, that both my static sites were down. Fixed them in the DNS records to get them back up and running. I guess I missed their announcement for the change in IP. #codebergpages

  16. @fredonline I’ve been looking out for an alternative too after this prolonged outage of Codeberg Pages for my static site deployment. #codeberg #codebergpages

  17. @fredonline I’ve been looking out for an alternative too after this prolonged outage of Codeberg Pages for my static site deployment. #codeberg #codebergpages

  18. Great news: Today, we have managed to distribute our Forgejo instance across two servers. A main instance still handles most traffic, but requests from #CodebergPages are now handled by another server. Going forward, we'll try to route more read-only traffic there to distribute the load.

    This is an important milestone, because such a setup was never tested with #Forgejo at this scale.

    This should improve availability of both Codeberg.org and Codeberg Pages.

    Details: codeberg.org/forgejo/discussio

  19. Great news: Today, we have managed to distribute our Forgejo instance across two servers. A main instance still handles most traffic, but requests from #CodebergPages are now handled by another server. Going forward, we'll try to route more read-only traffic there to distribute the load.

    This is an important milestone, because such a setup was never tested with #Forgejo at this scale.

    This should improve availability of both Codeberg.org and Codeberg Pages.

    Details: codeberg.org/forgejo/discussio

  20. Benutzt hier eigentlich jemand das Pages Feature auf Codeberg und kann mir sagen wie gut das funktioniert? Das feature ist ja wohl in einem Maintenance Mode wird also wohl derzeit nicht mehr weiter entwickelt.
    #codeberg #codebergpages

  21. Benutzt hier eigentlich jemand das Pages Feature auf Codeberg und kann mir sagen wie gut das funktioniert? Das feature ist ja wohl in einem Maintenance Mode wird also wohl derzeit nicht mehr weiter entwickelt.
    #codeberg #codebergpages

  22. Finally migrated my personal website (powered by #HugoSSG) from #GitLab to #Codeberg. Including #CI via #ForgejoActions and hosting via #CodebergPages. Jobs are running on the local #homelab server.

    There are jobs for building and deploying the website and for updating the contribution data through #contripy.

    So far this has been very smooth and straightforward. Though I still need to learn the new CI workflow syntax as I'm used to GitLab from the daytime job.

    #Forgejo #FOSS #gitforge

  23. Finally migrated my personal website (powered by #HugoSSG) from #GitLab to #Codeberg. Including #CI via #ForgejoActions and hosting via #CodebergPages. Jobs are running on the local #homelab server.

    There are jobs for building and deploying the website and for updating the contribution data through #contripy.

    So far this has been very smooth and straightforward. Though I still need to learn the new CI workflow syntax as I'm used to GitLab from the daytime job.

    #Forgejo #FOSS #gitforge

  24. @lorax @Codeberg Ich bin derzeit noch auf Codeberg Pages, werde aber bald selber hosten. Zum einen soll die Info zu meinem OpenPGP Public Key (codeberg.org/duxsco/) auf meiner eigenen Website erscheinen. Zum anderen werde ich Anubis (en.wikipedia.org/wiki/Anubis_() zum Schutz meiner Website (gentoo.duxsco.de/) einrichten. Aber noch muss ich noch einiges umschreiben, u.a. die Nutzung von Gentoo Cloud Images (gentoo.org/news/2025/02/20/gen) statt SystemRescueCD als Rettungspartition.

    #OpenPGP #Gentoo #Anubis #AI #Codeberg #codebergpages

  25. Hetzner Domain & Codeberg Pages

    Benutzt irgendwer in meiner timeline eine @hetzner Domain zusammen mit @Codeberg pages und hat das zum Laufen gebracht?
    Da es bei Hetzner keine alias gibt, versuche ich das ganze mit A, AAAA, Cname für www, txt , und dann noch CAA fürs @letsencrypt Zertifikat.
    .domains ist auch im root Codeberg folder

    Funktioniert leider noch nicht.

    Hat das irgendwer schon geschafft?

    #hetzner #codeberg #codebergpages #entshittification

  26. Hetzner Domain & Codeberg Pages

    Benutzt irgendwer in meiner timeline eine @hetzner Domain zusammen mit @Codeberg pages und hat das zum Laufen gebracht?
    Da es bei Hetzner keine alias gibt, versuche ich das ganze mit A, AAAA, Cname für www, txt , und dann noch CAA fürs @letsencrypt Zertifikat.
    .domains ist auch im root Codeberg folder

    Funktioniert leider noch nicht.

    Hat das irgendwer schon geschafft?

    #hetzner #codeberg #codebergpages #entshittification

  27. Just posted another blog post, touching on mental health and the move of my site to a new static site generator.

    tim-harrison.uk/posts/sixth-po

    #gohugoio
    #codebergpages

  28. Just posted another blog post, touching on mental health and the move of my site to a new static site generator.

    tim-harrison.uk/posts/sixth-po

    #gohugoio
    #codebergpages

  29. I used a custom Internet-domain for a Codeberg Pages (static) website, but am getting an error.

    The DNS (CNAME) we set up seems to work fine.

    Also, Codeberg Pages seems to successfully redirect from HTTP to HTTPS.

    But, when I go to the HTTPS version of the website, I get that error.

    ...

    Has anyone else seen this Codeberg Pages error before?

    #codeberg #codebergPage #codebergPages

  30. I used a custom Internet-domain for a Codeberg Pages (static) website, but am getting an error.

    The DNS (CNAME) we set up seems to work fine.

    Also, Codeberg Pages seems to successfully redirect from HTTP to HTTPS.

    But, when I go to the HTTPS version of the website, I get that error.

    ...

    Has anyone else seen this Codeberg Pages error before?

    #codeberg #codebergPage #codebergPages

  31. Help needed... can the #CodebergPages of #codeberg repos become subdirs of the "main" custom domain?

    Currently villares.lugaralgum.com is published from a pages repo on codeberg.org/villares/pages

    Can my /villares/other_repo/ page (from a pages branch I suppose) be published at villares.lugaralgum.com/other_repo ?

    (this is how GitHub Pages work by default, can it be replicated on Codeberg?)

  32. Help needed... can the #CodebergPages of #codeberg repos become subdirs of the "main" custom domain?

    Currently villares.lugaralgum.com is published from a pages repo on codeberg.org/villares/pages

    Can my /villares/other_repo/ page (from a pages branch I suppose) be published at villares.lugaralgum.com/other_repo ?

    (this is how GitHub Pages work by default, can it be replicated on Codeberg?)

  33. @madomado
    agreed! I really am surprised more people don't use it, especially to host a Static website using Codeberg pages.

    #codebergpages

  34. @madomado
    agreed! I really am surprised more people don't use it, especially to host a Static website using Codeberg pages.

    #codebergpages

  35. 🔔 #CodebergPages users with custom domains: Please check and update your DNS records.

    You are not affected if you directly use username.codeberg.page, or if you configured CNAME or ALIAS records.

    You are affected if you configured a custom domain with A and AAAA records before 19 April 2025.

    Please double-check that you use these records:

    A: 217.197.84.141
    AAAA: 2a0a:4580:103f:c0de::2

    We'll share more background on this change on our blog soon.

  36. 🔔 #CodebergPages users with custom domains: Please check and update your DNS records.

    You are not affected if you directly use username.codeberg.page, or if you configured CNAME or ALIAS records.

    You are affected if you configured a custom domain with A and AAAA records before 19 April 2025.

    Please double-check that you use these records:

    A: 217.197.84.141
    AAAA: 2a0a:4580:103f:c0de::2

    We'll share more background on this change on our blog soon.

  37. I've lost so many hours of sleep trying to make #codebergpages work.
    Just now I found out that while username.codeberg.page is served from the "pages" branch, custom domain pointing to username.codeberg.page is served from the "main" branch :nkoFacepalm:
    Compare stepanzak.codeberg.page and stepanzak.cc
    #codeberg

  38. I've refactored my 's on from using two repositories (`pages` and `pages-ssg`) to use only one (`site`) - with two branches - and added with !

    Somehow, personal tech is just too fun..!

    Site: maze88.dev
    Source: codeberg.org/maze/site

  39. I've refactored my #site's #SSG on #codebergPages from using two repositories (`pages` and `pages-ssg`) to use only one (`site`) - with two branches - and added #CI with #woodpeckerCI!

    Somehow, personal tech #tinkering is just too fun..!

    Site: maze88.dev
    Source: codeberg.org/maze/site

    #techBlog

  40. Oh, nice, Codeberg Pages supports proper HTTP redirects these days!

    docs.codeberg.org/codeberg-pag

    Including catch-alls like /my-spa/* to /my-spa/index.html 👍

    Thanks @Codeberg!

    #Codeberg #CodebergPages #HTTP #redirect #WebHosting

  41. Finally got part of my website setup on #codeberg pages at www2.claytonerrington.com/

    I think the problem was I wanted a subdomain for codeberg.claytonerrington.com, and having codeberg in the subdomain. Now to see what I want to move over.

    #codebergpages

  42. So pleased with my #mdBook progress:

    mas.to/@SustainableSailing/110

    I have my #Markdown sources under #Git version control on #Codeberg at codeberg.org/SustainableSailin

    The rendered HTML is on #CodebergPages at sustainablesailing.codeberg.pa

    The edit cycle is simple. Save, Commit, Sync the sources. Then build the HTML. Copy the files to the pages repository, Commit and Sync. I have a 3 line script to do the build & copy.

    I have plug-ins for wordcount, Admonish tags and to generate pdf's and epud all working 😃

  43. If you want to use the source in #emacs #OrgMode just head to the #codeberg repository it is hosted on. The blog is generated directly off of it into a static page.
    codeberg.org/Chfkch/nixos-pine

    #CodebergPages