Cookbook

Recipes for the situations that show up in real teams. Each page is a self-contained walkthrough you can adapt.

• Corporate proxy & TLS

  ---

  Get jarvy setup working through your company's HTTP proxy with custom CA bundles.

  Behind a corporate proxy

• Multi-project Postgres

  ---

  Run different Postgres versions for different projects on the same laptop without port conflicts.

  Side-by-side Postgres

• Monorepo with multiple roles

  ---

  Frontend, backend, and DevOps contributors share one repo but install only the tools they need.

  Monorepo role split

• Secrets via 1Password

  ---

  Pull [env.secrets] values from 1Password CLI instead of hardcoding or relying on each developer to set them.

  1Password integration

• GitHub Actions matrix

  ---

  Run jarvy validate and jarvy drift check across macOS, Linux, and Windows in CI.

  GitHub Actions matrix

• Slack notifier hook

  ---

  Notify a Slack channel when a contributor completes jarvy setup so the team can welcome them.

  Slack notifier

---

Recipe template

Every recipe follows the same shape:

1. Problem — what real situation triggered this recipe
2. Config — the jarvy.toml snippet
3. Why it works — what each piece does
4. Variations — common tweaks
5. Caveats — when this doesn't fit

If you have a recipe to contribute, open a PR — recipes are the highest-leverage contribution to the docs.