xenvsync

Examples

Command-first examples for real teams. This page shows how xenvsync is applied in actual day-to-day delivery, from solo development to enterprise release controls.

Scenario Matrix

TeamTypical ScalePrimary Outcome
Solo Developer1-2 engineersPrevent accidental plaintext leaks without adding process overhead.
Startup Team3-15 engineersShare staging and production secrets with per-member access and quick onboarding.
Enterprise Platform Team15+ engineers / multiple servicesStandardize secret controls with repeatable CI gates, audits, and revocation flow.

Team Playbooks

Solo Developer

Pain point: Local .env is edited constantly and can be committed by mistake.

Target outcome: Prevent accidental plaintext leaks without adding process overhead.

Solo Developer command flowbash
$ xenvsync init
$ xenvsync push
$ git add .env.vault
$ git commit -m "vault update"
$ xenvsync run -- npm run dev

Startup Team

Pain point: Team members share credentials over chat and CI environments drift from local setups.

Target outcome: Share staging and production secrets with per-member access and quick onboarding.

Startup Team command flowbash
$ xenvsync keygen
$ xenvsync whoami
$ xenvsync team add alice <alice-pubkey>
$ xenvsync team add bob <bob-pubkey>
$ xenvsync push --env staging
$ xenvsync push --env production

Enterprise Platform Team

Pain point: Inconsistent secret handling per repository and unclear offboarding confidence.

Target outcome: Standardize secret controls with repeatable CI gates, audits, and revocation flow.

Enterprise Platform Team command flowbash
$ xenvsync doctor
$ xenvsync verify --env production
$ xenvsync log --env production -n 30
$ xenvsync rotate --revoke former-member --env production
$ xenvsync push --env production

Continue Exploring

Workflow Library

Expanded end-to-end workflows for local, CI, release, and incident scenarios.

Open workflows

Usage Cookbook

Command recipes by intent: bootstrap, audit, migration, export, and recovery.

Open usages

Narrative Use Cases

Deeper context and tradeoff analysis across solo, startup, and enterprise teams.

Open use-cases