DevOps
CI/CD, containers, infrastructure as code, cloud and release plumbing.
Download all 28
Entries
Search and filter in DevOps- Design a deployment strategy
Chooses and specifies a deployment strategy (rolling, blue-green, canary or feature-flagged) with health gates, automated rollback triggers and database-change ordering. Use when deploys feel risky.
- Review a Dockerfile
Reviews a Dockerfile for security, image size, build cache use and runtime correctness, and returns ranked findings with a corrected file. Use before shipping an image, or when one is too big.
- Review an infrastructure plan before apply
Reviews a Terraform, OpenTofu or other IaC plan for destructive changes, security exposure, cost surprises and changes outside the stated intent. Use before running apply, especially in production.
- Write a Docker Compose dev environment
Writes a Docker Compose local development setup that mirrors production dependencies, with health checks, named volumes, seed data, env files and a one-command start. Use when onboarding developers.
- Write a GitHub Actions workflow
Writes a secure, cached and least-privilege GitHub Actions workflow that fits the repository's real build and test commands. Use when adding CI, a release job or a scheduled task.
- Automate mobile app signing
Sets up iOS provisioning and Android keystore signing in CI with certificate and profile management, secret storage, build numbers, test-track uploads and recovery from expired certificates.
- Build a firmware CI pipeline
Designs firmware CI with pinned containerised toolchains, a per-board build matrix, static analysis, host unit tests, per-PR size reports, signed artefacts and optional hardware-in-the-loop.
- Containerise an existing app
Containerises an existing app in gated steps, detecting the stack, writing a multi-stage Dockerfile and compose file, then building, running and documenting it. Use when an app has no containers yet.
- Deploy an app to a VPS
Takes an app from a fresh VPS to production with a non-root user, firewall, process manager, reverse proxy, TLS, repeatable deploys and rollback. Use when self-hosting on a single server.
- Design a CI/CD pipeline
Designs a CI/CD pipeline - stages, environments, promotion gates, caching, secrets and rollback triggers - and sketches the config for the chosen CI provider. Use when setting up delivery.
- Design over-the-air device updates
Designs over-the-air updates for a device fleet with A/B or swap partitions, signed images, staged cohort rollout, rollback on failed health checks, power and bandwidth limits and status tracking.
- Design a golden path template
Designs a paved-road service template for an internal platform, with repo skeleton, CI, deployment, observability and security defaults, ownership metadata, override rules and adoption measures.
- DevOps engineer
Acts as a DevOps engineer who automates the second time, keeps pipelines fast and reproducible, and makes every change reversible. Use for CI/CD, infrastructure and release work.
- Mobile app release track
Ships a mobile app release in gated steps, from release branch and freeze to QA and beta, store metadata and review notes, a staged rollout with crash gates, and post-release monitoring.
- Plan backups and disaster recovery
Writes a backup and disaster-recovery plan with RPO and RTO targets, dependency order, restore drills and owner checklists. Use when a system has backups nobody has restored, or no plan at all.
- Platform engineer
Acts as a platform engineer who runs the internal developer platform as a product, with golden paths, self-service over tickets, sensible defaults and adoption measured rather than mandated.
- Reduce cloud spend
Analyses a cloud bill or cost export alongside the architecture and ranks savings by monthly impact, effort and risk. Use when the cloud bill grows faster than usage.
- Release manager
Acts as a release manager who keeps releases boring with release trains, freeze rules, go/no-go checklists, staged rollouts, versioning, hotfix and backport policy, and clear communication.
- Release track
Takes a release from change review to changelog, checklist, staged rollout, verification and announcement, pausing for approval between steps. Use for any release users will notice.
- Set up a domain and HTTPS
Walks through pointing a domain at an app, with the exact DNS records, HTTPS certificates, redirects and a check after every step. Use when launching a site or moving it to a new host.
- Set up a game build pipeline
Sets up automated multi-platform game builds with headless engine builds, asset and library caching, build numbering, symbol upload, smoke tests and distribution to testers or store betas.
- Set up preview environments
Sets up a preview environment per pull request with build and deploy, seeded databases, scoped secrets, the URL posted to the PR, automatic teardown and cost limits.
- Speed up a CI pipeline
Analyses a slow CI configuration and its job timings, then proposes caching, parallelism and test splitting with the minutes each change saves. Use when builds are slowing the team down.
- Write a GitLab CI pipeline
Writes a .gitlab-ci.yml with stages, a needs graph, lockfile-keyed caching, rules, environments and secrets kept out of logs. Use when setting up or rebuilding CI/CD for a GitLab project.
- Write a Helm chart
Writes a Helm chart for a service with a validated values schema, shared helpers, probes, resources, per-environment values and safe upgrades. Use when a service needs a reusable, versioned chart.
- Write Kubernetes manifests
Writes production-ready Kubernetes manifests for a service with probes, resource requests, a disruption budget and a restricted security context. Use when deploying a service to a cluster.
- Write a reverse proxy config
Writes an nginx, Caddy or Traefik config for routing, TLS, forwarded headers, caching, compression and websockets, with test commands. Use when putting one or more services behind a proxy.
- Write a Terraform module
Writes a reusable Terraform module with typed, validated variables, secure defaults, documented outputs and an example. Use when wrapping cloud resources for other teams to consume.
Not: responding to a live production problem (incident).