Login
You're viewing the assemblag.es public feed.
  • Oct 17, 2026, 1:18 PM

    I'm trying to move my website from GitLab to @Codeberg and ngl a bit overwhelmed with trying to figure out how the CI works for git-pages.

    Can I use the CI or do I need to register before hand (I'm getting mixed signals) Is there a CI validation file somewhere so that I don't try to debug CI by just smashing it? Is there a cache for my PHP dependencies? How do I know all the extensions I need are in the 8.5-cli image? Yes I have a custom whacky static site generator, but it is my playground.

    💬 1🔄 1⭐ 2

Replies

  • Oct 17, 2026, 1:25 PM

    Is there also a way to test the deploy works *before* I point my domain name to it? All of this is very confusing to me :(

    I never really got GitHub Actions and so Forejo being based on that just really fucks with me. But then GitLab CI has become a monster of it's own now too compared to 2019 when I set it up.

    💬 0🔄 0⭐ 0
  • 💬 1🔄 0⭐ 0
  • Oct 17, 2026, 4:32 PM

    @Codeberg I did find that action, good to know I can just use it. Can I also use an image with it that included PHP or is that something that would require Woodpecker?

    💬 1🔄 0⭐ 0
  • Oct 17, 2026, 4:45 PM

    @Girgias yes, you can use different images in different steps of the pipeline, codeberg.org/git-pages/action has examples of that, using eg `actions/checkout@v7` for the cloning of the repo and then `actions/git-pages@v2` for the deployment of the output. You can similarly put an in-between action with a container of your choice for the actual build. ~b

    💬 0🔄 0⭐ 0