Examples gallery¶

Every template is a real, runnable jarvy.toml you can copy into your repo's root and ship today. Pick the closest match, edit the versions, commit.

# Copy from the repo
curl -fsSL https://raw.githubusercontent.com/Cliftonz/jarvy/main/examples/<template>/jarvy.toml \
  -o jarvy.toml
$EDITOR jarvy.toml
jarvy setup

Or use the CLI:

jarvy init --template node-pnpm

Language-specific¶

Template	Stack	Best for
`node-npm`	Node.js · npm	Vanilla Node services, libraries, CLI tools
`node-pnpm`	Node.js · pnpm	Monorepos, faster installs, strict dependency resolution
`node-bun`	Bun runtime	Edge functions, scripts, fast TypeScript builds
`deno`	Deno	Secure-by-default scripts and APIs
`python-api`	Python · pip · venv	FastAPI, Django, Flask APIs
`python-uv`	Python · uv	Modern, fast pip replacement; reproducible installs
`go-api`	Go · air · goose · golangci-lint	Go HTTP services with hot reload and migrations
`rust-cli`	Rust single-crate	CLI tools, focused libraries
`rust-workspace`	Rust workspace	Multi-crate Cargo workspaces
`ruby-rails`	Ruby on Rails · Postgres · Redis	Rails apps with full local services
`java-spring`	Java · Spring Boot	Maven or Gradle Spring services

Multi-service¶

Template	Stack
`react-app`	React + Vite frontend
`fullstack`	Frontend + backend + database, ready for `docker compose`
`k8s-platform`	Platform engineering: kubectl, helm, terraform, k9s, …

What every template includes¶

[provisioner]   # language runtime + universal CLI tools
[npm]/[pip]/[cargo]   # language-specific packages
[hooks]         # lockfile sync, completions, project setup
[env.vars]      # sensible defaults (NODE_ENV, PYTHONUNBUFFERED, …)
[commands]      # jarvy run tasks (npm-run style, incl. pre/post hooks) + interactive-menu entries
[drift]         # drift detection enabled with appropriate track_files

Customizing a template¶

Common edits:

Edit	When
Pin tighter — `node = "20.11.1"` instead of `node = "20"`	Reproducibility for releases or audits
Add roles — `role = ["frontend", "devops"]`	Mixed teams sharing one repo
Add `[network]` block	Behind a corporate proxy
Move secrets to `{ env = "VAR" }`	Anything sensitive — never hardcode
Tighten `[drift] version_policy`	Lock down patch versions for security-sensitive projects

Configuration reference →

Validate before committing¶

jarvy validate         # schema + value check
jarvy diff             # what would change on this machine
jarvy setup --dry-run  # full plan, no execution

Don't see your stack?¶

Open a discussion or contribute a template via PR — see the examples README for the contribution flow.