peak deploy archives your current directory, uploads it to Himalaya,
and streams build progress until the deployment is live.
peak deploy
Linking a project
The first time you run peak deploy in a directory, Peak asks which
Himalaya project to deploy to and remembers your choice in
.peak/project.json. Every later peak deploy in that directory
reuses the link -- no prompts.
Peak automatically adds .peak/ to your .gitignore if one exists, so
the link file never gets committed. If the directory has no
.gitignore, Peak leaves it alone rather than creating one unasked.
Targeting an environment
peak deploy --env staging
peak deploy -e preview
--env (short: -e) accepts production, staging, or preview,
and defaults to production if omitted.
What gets uploaded
Peak archives the project directory as a .tar.gz and uploads it
directly -- there's no separate build step on your machine, the build
happens on Himalaya. The archive always excludes .git/, and excludes
whatever your .gitignore excludes if the directory has one.