From manual deployment to a release pipeline
A web application with a .NET back end is deployed by copying files to a single server, and every release takes an evening and two people.
We write down every step of today's release, including the ones nobody documented.
A GitHub Actions pipeline builds, tests and scans every change.
The application runs in Docker containers, with staging and production described in code.
Production releases need an approval and can be rolled back in one click.
Releases happen during the working day, with a record of who approved what.
An illustrative example of the way we work, not a named customer.
