☁️DevOps & Cloud
Ship, deploy and run in the cloud · 34 terms
DevOps Basics
10The way of working behind shipping software, what a build makes, and the places an app runs before and after it goes live.
A way of working. The people who build the code also run it.
DevOps with safety checks at every step. They are not left to the end.
A team builds shared tools. Then other developers can ship on their own.
Five numbers that show how fast a team ships and how often it breaks things.
The step that turns source code into files that can run or be shipped.
The finished, saved output of a build, ready to ship.
One full place where a copy of your app runs, with its own settings.
Where you write and try code, most often on your own computer.
A copy of the live site. You use it for a last check before release.
The live one, where real users use the real app with real data.
CI/CD
9Letting a machine build, test and ship every change, and the tools that run those steps.
Merging code often. A machine builds and tests each change.
Keeping code ready to release at all times. Going live is one click.
Each change that passes the tests goes live on its own. No button.
The steps a machine runs on each change, from commit to live.
One step of a pipeline, like build, test or deploy. It holds jobs.
The machine that picks up a pipeline's jobs and runs them.
The CI/CD tool built into GitLab. You set it up in a .gitlab-ci.yml file.
A free tool you run on your own servers. It builds, tests and ships code.
The CI/CD tool built into GitHub. You set it up with a YAML file.
Deployment
9Putting a new version on live servers, the plans for swapping old for new, and the ways to undo it.
Putting a new version of your app on the servers. Then users get it.
The plan for how a new version takes the old one's place on live servers.
Run two full copies, then move all traffic from the old to the new.
Give a new version to a few users first, then to more and more.
Swap the old version out one server at a time, so the site stays up.
Ship a new version while the site stays up the whole time.
Put the last version that worked back after a bad deploy.
A switch in your code. It turns a feature on or off with no deploy.
A short-lived copy of the app for one pull request. It has its own link.
Infrastructure as Code
6Writing servers and networks down as files a tool builds, and what happens when the real setup wanders off.
Write your servers down in text files, and a tool builds them for you.
A tool that builds cloud setups from text files. The files say what should exist.
Using code to keep many servers set up the same way.
A tool that sets up many servers at once. It reads its steps from a YAML file.
Run your systems from a Git repo. A helper keeps them in line with it.
When the real setup drifts away from what the files say.