Driftwood Ale Works is a fictional brewery, made up for a Citrix DaaS automation demo. There's no beer for sale here. About this site

How we brew

The recipe is the repository

Driftwood's virtual desktops run on Citrix DaaS in Azure. Nobody builds them by hand. They're defined in Terraform, changed through pull requests, and rebuilt by a pipeline.

Illustration of Ellie Sorensen holding a laptop with stickers reading Automate, Rebuild, Repeat

Two ways to run a brewery

Click-Ops vs. GitOps

Click-Ops

  • Manual changes through wizards and consoles
  • No record of who changed what, or why
  • Configuration drifts quietly over time
  • Knowledge lives in people's heads
  • Every environment ends up a little different

GitOps

  • Every change is a pull request
  • Full history: what changed, who approved it, and why
  • The environment is rebuilt, not patched, so drift can't build up
  • The repository is the documentation
  • Every environment matches the code, every time

The brewhouse

What the crew built

01

GitHub

The source of truth for the environment, and where every approval is recorded.

02

Terraform

Declarative infrastructure as code. The environment is described, not scripted step by step.

03

GitKraken

A visual Git client, so the whole crew can follow branches and merges.

04

VS Code

Where the environment actually gets edited.

05

Azure + Citrix DaaS

Where it all runs.

Three environments, one pipeline

Every image is tasted twice before it's poured

A new desktop image starts in Dev, moves to Test for validation, and only then reaches the desktops people use.

1Dev

Machine built with every new image

3Test

Machines for validation before production

5Production

Desktops end users see

Rebuilt every 30 days, on purpose

Consistency isn't maintained. It's regenerated.

  • The full environment is torn down and rebuilt on a schedule
  • Same Terraform, same pipeline, every single time
  • There's no "old" environment left around to drift
Illustration of Ellie Sorensen, Cellar Master, crouched beside a keg with a Cellar Cycle checklist

Humans still decide

Automation handles the how. People own the when.

  • Cutover gate: a person signs off before a new image goes live
  • Decommission gate: a person signs off before the old one is torn down
  • Every approval is logged and auditable

This website ships the same way. A change merges, then waits for an approval before it reaches production.

Illustration of Priya Chandrasekaran reviewing a tablet, pen in hand

Why this is also a security story

Fewer hands on the controls

Reviewed

Every change is peer-reviewed before it ships.

No standing admin

The pipeline acts, not a person clicking around a console.

Short-lived

Regularly rebuilt environments shrink the window an attacker has to work with.

Audited

A complete trail of every change and every approval. Secrets live in a vault, not typed into a wizard.