LemonadeHost help Main site Pricing Status

For developers

Publishing from the command line

One command publishes a folder. The CLI has zero dependencies, so npx downloads one package and runs it.

npx lemonade-host@latest deploy ./dist
The package is lemonade-host, not lemonade. The bare name belongs to somebody else. Installing the wrong one and handing it a deploy token gives a stranger's package your credential.

Commands

CommandWhat it does
lemonade deploy [folder]Zip the folder and publish it. Defaults to your built output.
lemonade statusThe last few deploys for this site.
lemonade loginSave a token and site id to ~/.lemonade.
lemonade whoamiCheck the token, and which site it reaches.

Options

FlagMeaning
--token lm_…A deploy token. Or set LEMONADE_TOKEN.
--dir FOLDERWhich folder to publish. Same as the positional argument.
--site st_…Which site. Only needed if the token reaches more than one.
--origin URLPoint at another instance, e.g. staging.
--yes, -yDo not ask before publishing. Use this in CI.
--jsonMachine-readable output.
--include-hiddenPublish dotfiles and node_modules too.
--version, -vPrint the version.
--help, -hUsage.

What gets left behind

By default the CLI skips dotfiles, node_modules, and the usual build detritus — so a stray .env in your output folder is not published by accident. --include-hidden turns that off, and you should know why you are reaching for it.

Symlinks are skipped, never followed. A link pointing outside your folder cannot drag anything in with it.

In CI

- name: Publish
  run: npx lemonade-host@latest deploy ./dist --yes --json
  env:
    LEMONADE_TOKEN: ${{ secrets.LEMONADE_TOKEN }}

--yes because there is nobody to answer a prompt, and --json so a failing step gives your logs something parseable. The command exits non-zero when a publish is refused.

Getting a token

Portal → your site → Deploy tools → create a token. It is shown once and stored hashed; if you lose it, revoke it and make another. See deploy tokens for what one can and cannot reach.

Last checked against the product on 2026-09-04. Something wrong or missing? Tell us.