ddev/ddev.com

Establish deployment pipeline

Closed this issue · 5 comments

mattstein commented

We’ll need to be able to manually build and deploy the site, and also have builds get triggered from WordPress when new posts are ready.

  • identify target infrastructure (Platform.sh, GitHub Pages, Vercel, etc.)
  • identify CDN (Cloudflare, etc.)
  • establish pipeline (probably with GitHub Actions)
mattstein commented

I think the working plan is that we’ll...

  1. Build the site with GitHub Actions.
  2. Commit the built files to an intermediary repository.
  3. Have Platform.sh listen to the build repo to pull and host changes.
  4. Use Cloudflare for fully-static edge caching on the apex domain.
mattstein commented

I’ve got a GitHub Actions workflow running that should be easy to adjust for deployment infrastructure.

It separates its work into two distinct jobs, build and push. Example: https://github.com/drud/ddev.com-front-end/actions/runs/4029253773

The build job generates the site and uploads the result as an artifact. The push job then downloads that artifact and commits it to https://github.com/drud/ddev.com-build, where my current VPS listens for commits, pulls them, and uses a simple shell script to purge Cloudflare’s cache.

We can do the same thing from Platform.sh when it’s time, and this could easily be adapted to include tests or future workflow enhancements.

mattstein commented

@rfay Drawing your attention to this in case it was too sneaky and you have any feedback. Seems to be working well!

rfay commented

Thanks!

I finally subscribed to everything on this repo, sorry that I hadn't done that before.

  • 😄1
mattstein commented

No need to apologize. I’m pretty chatty with myself so I imagine it’ll be a bittersweet subscription.