tezvyn:

☁️DevOps & Cloud

Infrastructure, containers, CI/CD, and cloud

125 bites

CI/CD & Automation30 sec read

GitHub Flow: A Simple, Branch-Based Workflow

GitHub Flow is a simple workflow where `main` is always stable and new work happens on a feature branch. It's used for continuous delivery, from code to documentation.

CI/CD & Automation32 sec read

Pull Requests: A Structured Conversation About Code

A Pull Request (PR) is a structured conversation about a proposed code change. It's used in team projects to review new features and fixes, ensuring quality and sharing knowledge. The footgun is treating PRs as a rubber-stamp approval instead of a real review.

CI/CD & Automation30 sec read

Distributed Version Control (DVCS): Everyone Gets a Copy

A DVCS gives every developer a full, independent copy of the repository, history and all. This is Git's model, making commits and branches instant because they're local. The footgun: your local copy isn't the team's truth until you push and pull to sync.

CI/CD & Automation30 sec read

GitOps: Your Git Repo is the Single Source of Truth

GitOps makes a Git repo the single source of truth for your infrastructure's desired state. An automated process makes production match what's declared in Git, enabling continuous deployment.

CI/CD & Automation32 sec read

Blue-Green Deployment: Zero-Downtime Releases

Run two identical production environments, Blue (live) and Green (new). To deploy, just flip a switch routing traffic to Green. This enables zero-downtime releases and instant rollbacks. The footgun is using DNS for the switch, which can lag due to caching.