Deploy to GitHub-Pages via Pipeline or Action? #221
-
I would like to deploy a small demo project for a theme to GitHub Pages (see suchja/statiq-dopetrope-demo. Now I came across statiq's official deployment guide GitHub Pages and understood that statiq should be run via GitHub Actions, but that it includes its own deployment pipeline for GitHub Pages. I tried that way many times with different settings, permissions, ... but can't get it working. Now looking into other repositories utilizing statiq to publish a GitHub Page I found the way to purely use GitHub Actions to deploy the contents. So basically it means that statiq is used to generate the static site, but its deployment pipeline is NOT used. Instead the appropriate actions are used. Which is the "better" way and why is the pipeline way not working??? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
There's definitely not a "better" way and both are totally valid. I personally like to keep everything in CI/CD scenarios contained in a single command line application and have that do the driving, so the use of a deploy phase where Statiq itself uploads to GitHub Pages comes from that personal preference. That said, there are a lot of reasons why leveraging built-in actions/steps/tasks that are native to the CI/CD environment could be preferred - for example, their use might enable some interesting functionality beyond what's available through Statiq, or allow deployment to locations that Statiq doesn't yet support (like Azure Static Web Apps or Cloudflare Pages). As for the problems with GitHub Pages deployment via Statiq, it looks like maybe the discussion happening in https://github.com/orgs/statiqdev/discussions/148 is related? If not, let me know and I'll dive a little deeper. |
Beta Was this translation helpful? Give feedback.
There's definitely not a "better" way and both are totally valid. I personally like to keep everything in CI/CD scenarios contained in a single command line application and have that do the driving, so the use of a deploy phase where Statiq itself uploads to GitHub Pages comes from that personal preference. That said, there are a lot of reasons why leveraging built-in actions/steps/tasks that are native to the CI/CD environment could be preferred - for example, their use might enable some interesting functionality beyond what's available through Statiq, or allow deployment to locations that Statiq doesn't yet support (like Azure Static Web Apps or Cloudflare Pages).
As for the problems wi…