Devops terms
Shipping fast, breaking nothing, sleeping soundly
The gap between writing code and running it reliably in production is where DevOps lives. CI/CD pipelines, infrastructure as code, containerisation, deployment strategies, monitoring, and incident response — this category covers the culture, tools, and practices that let teams ship with confidence and recover quickly when things go wrong.
Internal Developer Platform (IDP)
A curated, self-service layer on top of cloud and CI/CD infrastructure that product teams use to ship services without filing tickets — paved roads that make the right thing the easy thing.
3w ago
devops intermediate
Docker HEALTHCHECK
A Dockerfile instruction that defines how Docker tests whether a container is healthy — enabling automatic restart and load balancer removal on failure.
1mo ago
devops intermediate
Dockerfile builds using multiple FROM stages — build dependencies (Composer, Node, test tools) in earlier stages, copy only production artifacts to the final minimal image.
2mo ago
devops intermediate
Kubernetes for PHP Developers PHP 5.0+
The essential Kubernetes concepts PHP developers need — Pods, Deployments, Services, ConfigMaps, Secrets, and Ingress — for deploying and scaling PHP applications on Kubernetes.
2mo ago
devops intermediate
nginx + PHP-FPM Production Config PHP 5.0+
The canonical nginx + PHP-FPM setup for PHP production — nginx handles static files and slow clients, PHP-FPM runs PHP via FastCGI, with proper timeout, buffer, and security settings.
2mo ago
devops intermediate
On-Call Culture & Runbooks
Sustainable on-call practices — fair rotation, blameless postmortems, actionable alerts, and well-maintained runbooks that reduce mean time to recovery and prevent burnout.
2mo ago
devops intermediate
Shift-Left Testing
Moving testing earlier in the development process — catching bugs at the developer's machine and PR stage rather than in staging or production.
2mo ago
devops intermediate
Alerting & On-Call PHP 5.0+
Automated notifications triggered when SLIs breach SLO thresholds — effective alerting is actionable, low-noise, and tied to clear runbooks.
2mo ago
devops intermediate
Blameless Post-Mortem PHP 5.0+
A structured review of an incident focused on systemic causes and improvements, not individual blame — making it safe to surface failures.
2mo ago
devops intermediate
Maintaining two identical production environments and switching traffic between them for zero-downtime releases and instant rollback.
2mo ago
devops intermediate
Gradually routing a small percentage of traffic to a new release, monitoring for issues before a full rollout.
2mo ago
devops intermediate
Security practices for building and running containers — minimal base images, non-root users, read-only filesystems, image scanning, and runtime security controls.
2mo ago
devops intermediate
Packaging PHP applications and their dependencies into Docker containers for consistent, reproducible environments from dev to production.
2mo ago
devops intermediate
Automatically deploying every commit that passes CI to production, eliminating manual release steps.
2mo ago
devops intermediate
Strategies for reverting a broken deployment quickly — from git revert and re-deploy to instant traffic switching with blue-green or feature flags.
2mo ago
devops intermediate
Four metrics from the DevOps Research and Assessment team that predict software delivery performance: deployment frequency, lead time, change failure rate, and time to restore.
2mo ago
devops intermediate
Release toggles, ops toggles, experiment toggles, and permission toggles — each with different lifespans, owners, and removal disciplines.
2mo ago
devops intermediate
GitFlow uses long-lived feature and release branches; trunk-based development merges to main frequently — the latter scales better with CI/CD.
2mo ago
devops intermediate
Automating PHP CI/CD with GitHub Actions — running tests, static analysis, code style checks, and deployments on every push and pull request.
2mo ago
devops intermediate
Servers are never modified after deployment — to update, you build a new image and replace the old server entirely, eliminating configuration drift.
2mo ago
devops intermediate