devsync init

Synopsis

devsync init [repository]

Description

devsync init bootstraps your devsync setup. It either creates a brand-new local sync repository or clones an existing remote repository into the standard location at ~/.config/devsync/sync/.

When run without a repository URL, it initializes a fresh git repository and generates a new age encryption key. When a URL is provided, it clones that repository and prompts you to supply the corresponding age private key needed to decrypt any secrets stored there.

After initialization, devsync creates:

• ~/.config/devsync/sync/ — the sync repository directory
• ~/.config/devsync/settings.json — runtime settings (active profile, identity path, etc.)
• ~/.config/devsync/age/keys.txt — age key storage

Arguments

Argument	Description
repository	Optional. A git repository URL to clone (HTTPS or SSH).

Options

Flag	Description
--identity PATH	Persist the path to an age identity file in settings.json. Useful when your key lives in a password manager export or a separate secure location.
--key KEY	Pass an age private key (AGE-SECRET-KEY-…) directly. Useful for non-interactive or scripted setup.
--recipient AGE1...	Add an age recipient public key. Can be repeated to add multiple recipients. Enables sharing encrypted secrets with other users.
--verbose	Print detailed output during initialization.

Examples

New repository

# Create a new local sync repository with a fresh age key
devsync init

Clone existing

# Clone an existing sync repository from GitHub
devsync init https://github.com/yourname/dotfiles.git

Clone with key

# Clone and supply age key non-interactively
devsync init https://github.com/yourname/dotfiles.git \
  --key AGE-SECRET-KEY-1QQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQQ

External identity file

# Point devsync to an age identity file stored elsewhere
devsync init --identity ~/.secrets/age-identity.txt

Team recipients

# Add multiple recipients so teammates can decrypt secrets
devsync init \
  --recipient age1alice... \
  --recipient age1bob...

Notes

Note

Running devsync init a second time in the same environment will overwrite settings but will not destroy existing sync data. It is safe to re-run if you need to update the age identity path or add new recipients.

Caution

When using --key, your age private key will appear in your shell history. Prefer --identity with a key file, or run the command with a leading space (history suppression) on supported shells.

After initialization, track your first file with devsync track, then push with devsync push.