Not open yet — signups haven't started. Join the list for the day they do.

Command line

One command, from wherever your files are

Run npx lemonade deploy from your project folder. Nothing to install first, and it prints the live URL the moment it's done.

terminallive
$ npx lemonade deploy ./dist

› reading ./dist — 42 files
› uploading
› queued — position 1
✓ portfolio.lemonadehost.com

See it run

The whole interaction, start to finish

~/petloop — npx lemonade deploy
$ npx lemonade deploy Reading LEMONADE_TOKEN from the environment… Packing ./dist (42 files, 1.8 MB) Queued — 1 deploy ahead of yours Publishing… Live → https://petloop.lemonadehost.com

Install-free usage

Three steps, no setup

  1. Open a terminal in your project folder

    Wherever your built files live — the project root, or a build folder like /dist.

  2. Run the command

    npx lemonade deploy. npx fetches it for that one run — nothing to install globally, nothing to add to your project first.

  3. Read the URL it prints

    The deploy queues, publishes, and the command prints the live address before it exits.

The command and its flags

One command, a couple of options

# from your project folder
npx lemonade deploy

# point at a specific folder, if it's not the current one
npx lemonade deploy --dir dist

# pass a token instead of using the saved one
npx lemonade deploy --token lm_xxxxxxxxxxxxxxxx
FlagWhat it does
--dirDeploys the folder you point at instead of the current one.
--tokenAuthenticates the deploy without reading it from the environment.

Authenticating

A token, not a password

Generate a token from your account and either pass it with --token or set it once as LEMONADE_TOKEN in your shell. The CLI reads the environment variable automatically, so most people set it and never touch --token again. Like every Lemonade Host token, it's scoped to deploying — publishing a build and checking its status, nothing that touches billing.

In CI

The same command, running unattended

Add the token as a secret in your CI provider, export it as LEMONADE_TOKEN, and run the same command as a build step. It queues the same as a deploy from your laptop, so a pipeline that fires on every commit still publishes in order.

# example CI step, any provider that runs a shell command
- run: npx lemonade deploy --dir dist
  env:
    LEMONADE_TOKEN: $LEMONADE_TOKEN

Questions

What people ask about the CLI

Do I need to install anything first?

No — npx fetches the tool for that one run. There's nothing to install globally and nothing to add to your project.

Where do I get a token?

Generate one from your account and set it as LEMONADE_TOKEN, or pass it with --token. Like every Lemonade Host token, it's scoped to deploying only.

Can I run this in CI?

Yes — add the token as a secret in your CI provider, export it as LEMONADE_TOKEN, and run the same command as a build step.

Does the CLI build my project first?

No — we don't run a build on our side. Point --dir at the folder your own build already produced.

Prefer a different route?

The other three ways in

Run the command and you're live

See what's included on the static hosting page, or check pricing.

Join the list