Back to Install

Command Reference

Interactive Mode

hetge

Launches interactive mode with a menu of all available actions. Best for day-to-day use — guides you through each step with prompts and confirmations.

Environment Commands

hetge env:pull --force

Downloads .env files from 1Password using your .tpl template files. Templates define which secrets to fetch. Use --force to overwrite existing local files without prompting.

hetge env:push --force

Uploads local .env files back to 1Password. Syncs any changes you've made locally to the vault. Use --force to overwrite vault items without prompting.

Build & Deploy Commands

hetge build --deploy

Builds a Docker image and pushes it to GitHub Container Registry (GHCR). Tags the image with both the version from package.json and latest. Add --deploy to automatically trigger deployment after a successful build. Requires a running Docker daemon (with buildx) and a GitHub login with write:packages — both are checked automatically, and the CLI will prompt for gh auth login if needed.

hetge deploy

Triggers a deployment on Dokploy using the existing image on GHCR. No rebuild occurs — this just deploys what's already been pushed.

hetge sync --deploy

Creates or updates your project configuration on Dokploy. Sets up the project, environment, compose file, and domain. Run this first when setting up a new project. Add --deploy to trigger deployment after syncing.

Account

hetge login

Refreshes GitHub authentication (with write:packages) and, if the build feature is enabled, forces a fresh docker login ghcr.io using the current gh token. Use this if your token expired or you switched GitHub accounts mid-session.

Typical Workflow

1
hetge sync
First time only — creates your project on Dokploy
2
hetge build --deploy
Build image, push to GHCR, and deploy in one step
hetge build --deploy
Repeat for subsequent deployments

Notes

Dokploy settings (URL, API key, domain, etc.) are stored in .env.deploy.local
When .tpl templates are updated, run env:pull to fetch the latest secrets
After modifying .env files locally, run env:push to sync to 1Password, then sync to update Dokploy
When compose.yml or .env.deploy.local changes, run sync to update Dokploy
Docker must be installed and running for build. The CLI verifies the daemon on every build and prints platform-specific hints (e.g. open -a Docker on macOS) if it's missing or stopped