Continuous Deployments for WordPress Using GitHub Actions | CSS-Tricks

Continuous Integration (CI) workflows are considered a best practice these days. As in, you work with your version control system (Git), and as you do, CI is doing work for you like running tests, sending notifications, and deploying code. That last part is called Continuous Deployment (CD). But shipping code to a production server often requires paid services. With GitHub Actions, Continuous Deployment is free for everyone. Let’s explore how to set that up.

Source: Continuous Deployments for WordPress Using GitHub Actions | CSS-Tricks

Ever wonder how a big site like Stack Overflow handles code deployment?

We’ve talked about Stack Overflow’s architecture and the hardware behind it. The next most requested topic was Deployment. How do we get code a developer (or some random stranger) writes into production? Let’s break it down. Keep in mind that we’re talking about deploying Stack Overflow for the example, but most of our projects follow almost an identical pattern to deploy a website or a service.

Source: Nick Craver – Stack Overflow: How We Do Deployment – 2016 Edition

Fascinating look into how Stack Overflow code gets from a developers workstation to production servers. There are many good ideas about development workflow in here.