Skip to content

View slides

DevOps for Foundlings

Yehuda Deutsch


What is DevOps?

DevOps is whatever stops "it works on my machine" from becoming "it's broken for everyone else"

  • What is your Dev role?
  • What is your Ops role?
  • How big is your Dev/Ops gap?
  • Where are your current release pains?

Who am I?

Yehuda Deutsch

Software Developer with a sweet tooth for infrastructure

Principal DevOps Engineer at Palo Alto Networks SDLC / Internal Platform

Open Source / Data / Knowledge activist

Self Hoster


Define your route

The highway is not always the fastest route, and a fast car might not always get you where you need

  • How many users?
  • How many developers?
  • What's the cost of downtime?
  • What's your budget?

Define your MVP

Your MVP is the smallest thing that works for someone who isn't you

  • What's the one job this product does?
  • What can break without anyone caring?
  • What does "shippable" mean for you?
  • What's deliberately out of scope?
  • Would you use it as-is?

Version your source code

Version control isn't just about the code - it's your safety net, your history, and your rollback button

  • Everything in git
  • Tag your releases
  • Keep branches simple
  • Treat your deploy script like code
  • Source of Truth

CI/CD is about guardrails

CI/CD isn't about fancy pipelines - it's the thing that catches you before you hit the ditch

  • CI catches your mistakes
  • CD prevents the scary deploy
  • It protects you from yourself
  • Start with one file
  • A green pipeline is trust

Environments

You really need two: one to break things, one to serve users. The rest are different degrees of acceptable breakage

  • Production
  • One non-production
  • Same config, different values
  • Skip the environment zoo

Configuration and Secrets

One .env file committed to git is all it takes to ruin your week

  • Config is sourced from environment variables
  • Same build, every environment
  • Secrets never in git
  • If you leak a key, rotate it immediately

Observability

You don't need Datadog, You need to know your app is down before your client emails you

  • The minimum viable monitoring - Is it up? Is it erroring? Is it slow?
  • Get an alert when something breaks
  • Read your logs
  • Alert on symptoms, not noise

Rollbacks and Charge Ahead

If you can't roll back, every deploy is a gamble - Small projects can't afford gambles

  • Keep the previous version
  • One-command rollback
  • Health checks matter
  • Deploy small, deploy often
  • Hotfix should be a normal deployment

The Lo Ta'asses (Don'ts)

  • Don't jump to buzz tools because of the buzz
  • Orchestration is an obstacle when you don't need it
  • Microservices will split your mind if used too early
  • Don't over compensate with tools, use the few systems that do more than use many tools that cover all
  • Don't be a "Poshet Yad" (Beggar)
  • Don't let an "Eved Ki Yimloch" situation (Reverse Position)
  • Security Fatigue is real and mean - don't overprotect

ATAQ?


This is the way

x59.us

y@x59.us

gitlab.com/uda/talks