GitOps for Basil: Automating an Urban Garden Without Overengineering It

Sabrina Holt — Wed, 01 Oct 2025 19:50:26 +0000

Picture This: Version Control for Your Basil

If you’ve ever tried to keep a basil plant alive on a city balcony while also debugging distributed systems, you’ve probably had a recurring thought: Wouldn’t it be easier if I could just git push my watering schedule? — or maybe that’s just me. Either way, here’s the story of how I used a little GitOps thinking to automate my urban herb garden… without turning it into a DevOps death spiral.

The "Why" (Besides Needing Pesto on Demand)

I’m a big fan of automating the boring stuff. But I’ve seen far too many tech projects (and yes, garden projects!) become so tightly wound around automation that no actual human wants to touch them anymore. My goal here: Let code do the heavy lifting, but always keep a manual override (because maybe I want to water my basil after a tricky deploy—it’s therapeutic, okay?).

What is "GitOps for Basil"?

For the uninitiated, GitOps is a strategy where your system's desired state lives in Git, and automation (usually bots or controllers) brings the actual system in line with what's declared there. Think of it as a way to manage your software—or in this case, your plants—with the careful versioning and review process that developers love.

In garden terms: Define watering patterns and light schedules in a plain text file (garden.yaml), commit to GitHub, and a little Raspberry Pi on my shelf reads those declarations and tells a smart relay to water the basil. If I change the config, commit, and push—the garden follows suit. If I break everything, a quick git revert returns my basil to its (hopefully lush) glory.

The Minimal Viable Automation Stack

I promised not to overengineer. Here’s what I actually used:

Raspberry Pi Zero (with Wi-Fi)
Moisture sensor (trusty capacitive, thanks Adafruit)
Simple peristaltic pump
Relay/Power controller
LED Grow Light (bonus: makes my living room look like a spaceship)
Python Scripts (for pulling from Git, reading YAML, interfacing with GPIO)
GitHub Actions (for fun and a little CI/CD flair)

The config file (`garden.yaml`):

basil:
  moisture_min: 35    # below this, trigger watering
  moisture_max: 60    # stop watering here
  light_on: "07:00"
  light_off: "20:00"

The Sync Script (abridged magic):

import yaml
import requests
from datetime import datetime

def load_garden_config(git_raw_url):
    resp = requests.get(git_raw_url)
    config = yaml.safe_load(resp.text)
    return config['basil']
# ... logic to read sensors, control relays, etc

Nerd note: Python is intentional here—it’s fast to hack, easy to debug after midnight, and plays nicely with Pi GPIO.

The Manual Override

There’s a big red button. No, really. It waters everything when pressed. Felt important.

Keeping it Human-Scale

Here’s where I draw the line: No Kubernetes. No web UIs (except the garden’s readme on GitHub). If I found myself writing a Helm chart for this setup, I’d know I’d gone too far.

The goal is reliability and tweakability. If I go on vacation, my plants survive. If I have a wild idea ("Does basil like jazz at night?"), it’s a one-line config change. And if my neighbor’s dog knocks the pump over, I can still just water the plants with a cup.

Photos! [Insert photo of a Pi nestled between tomato vines, LED aglow, and code open in VSCode on my balcony table.]

Lessons Learned

Automate, don’t alienate: Good automation invites you in, doesn’t lock you out.
Keep it observable: Logs to the garden GitHub repo keep me honest—and fixable.
Never skip the override: Machines are great, but sometimes you just need to press a big red button.

Urban gardening doesn’t have to be another overengineered mess. But a little version control never hurt anyone—except maybe my first batch of parsley, but that’s a story for another post.

Happy growing! 🌱

The $100 Climate Stack: Spend to Save the Planet, One Benjamin at a Time

Sabrina Holt — Wed, 01 Oct 2025 19:41:09 +0000

The $100 Climate Stack: Spend to Save the Planet, One Benjamin at a Time

Let’s nerd out on where your money can be a literal planet-saving power-up! 💸🌎

I get it: "Fixing the climate crisis" feels like it’s in the domain of governments and billionaires. But if you have $100 to intentionally throw at the problem, you can make shockingly measurable impact now. Let’s break down how to build your own $100 Climate Stack—an actionable combo of spending, donating, and investing that squeezes every last carbon molecule out of your dollar.

Stack Component 1: Direct Carbon Offsets

Best bang: Buy high-quality, verifiable offsets (not all are created equal!) targeting removal, not just avoidance. Think: Charm Industrial Bio-oil Injection, Climeworks Direct Air Capture (pricey but gold-standard), or cool projects aggregated by destroycarbon.com.
$25 here gets you 0.25-0.5 tonnes of CO₂ straight-up removed from the atmosphere;
Bonus nerd stat: That’s the equivalent of driving a gas car for 700-1,400 miles—gone!

Stack Component 2: Policy and Advocacy

Why this matters: Personal action is legit, but systemic change? That’s where we go turbo. Organizations like Clean Air Task Force and Evergreen Action punch above their weight, pushing governments to flip huge levers.
$20–30 here subsidizes months of lobbying and research in key energy and climate fights.
Trade-off tip: Boring-sounding orgs sometimes have the highest impact/$.

Stack Component 3: Frontier R&D and Innovation

Supporting the next big thing: Climate solutions aren’t just wind turbines and Teslas. There’s wild stuff like algae farms, new batteries, and low-carbon cement in the pipeline.
Try $10–20 as a micro-investment/donation through platforms like Stripe Climate or Carbon180, a nonprofit funding moonshot R&D.
Nerd takeaway: 1 in 10 bets here is like buying Bitcoin in 2011—huge leverage, uncertain payoff.

Stack Component 4: Climate Education and Movement Building

Amplify your own impact: Good info is contagious. Support newsletters, translation projects, YouTubers, or teachers talking climate science straight.
$10 here supercharges stories that shift hearts and votes (and prevents climate doomscrolling paralysis).

Stack Component 5: Personal Infrastructure

Low-hanging fruit: Upgrade your routine. Maybe you buy a plug strip, bike repair, vegan trial groceries, or pay the premium for renewable electricity (just $10–20 covers a meaningful slice for a month!).
Yes, it’s a multiplier: You get co-benefits—often more comfort, health, and a bit of bragging rights.

Sample $100 Climate Stack

$25: Permanent carbon removal offsets
$25: Policy/advocacy org pushing for macro change
$15: Donate to climate innovation/R&D
$10: Support science communication or teaching
$15: Buy an energy-saving item or try a climate-friendly product
$10: Your wild card! (Plant trees? Eco YouTuber? Open-source climate code?)

It’s not just about guilt or virtue signaling. Every dollar here is a force multiplier. Stack up, track your impact, and challenge friends with their own $100 climate recipe!

Want to Go Deeper?

You’ve got $100. That’s huge. Drop your stack ideas and favorite picks in the comments! 👇🌱

Forem: Sabrina Holt

GitOps for Basil: Automating an Urban Garden Without Overengineering It

Picture This: Version Control for Your Basil

The "Why" (Besides Needing Pesto on Demand)

What is "GitOps for Basil"?

The Minimal Viable Automation Stack

The config file (garden.yaml):

The Sync Script (abridged magic):

The Manual Override

Keeping it Human-Scale

Photos! [Insert photo of a Pi nestled between tomato vines, LED aglow, and code open in VSCode on my balcony table.]

Lessons Learned

The $100 Climate Stack: Spend to Save the Planet, One Benjamin at a Time

The $100 Climate Stack: Spend to Save the Planet, One Benjamin at a Time

Stack Component 1: Direct Carbon Offsets

Stack Component 2: Policy and Advocacy

Stack Component 3: Frontier R&D and Innovation

Stack Component 4: Climate Education and Movement Building

Stack Component 5: Personal Infrastructure

Sample $100 Climate Stack

Want to Go Deeper?

The config file (`garden.yaml`):