Command line
Run npx lemonade-host deploy from your project folder. Nothing to install first, it prints the live URL the moment it's done, and it's the same command in CI as on your laptop.
$ npx lemonade-host deploy ./dist › reading ./dist — 42 files › uploading › packing — 42 files, 1.8 MB ✓ portfolio.lemonhosted.com
See it run
Install-free usage
Wherever your built files live — the project root, or a build folder like /dist.
npx lemonade-host deploy. npx fetches it for that one run — nothing to install globally, nothing to add to your project first.
It packs the folder, uploads it, and prints the live address before it exits.
The command and its flags
# from your project folder npx lemonade-host deploy # point at a specific folder, if it's not the current one npx lemonade-host deploy --dir dist # pass a token instead of using the saved one npx lemonade-host deploy --token lm_xxxxxxxxxxxxxxxx
| Flag | What it does |
|---|---|
--dir | Deploys the folder you point at instead of the current one. |
--token | Authenticates the deploy without reading it from the environment. |
Authenticating
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
Add the token as a secret in your CI provider, export it as LEMONADE_TOKEN, and run the same command as a step in your pipeline. It queues exactly like 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-host deploy --dir dist env: LEMONADE_TOKEN: $LEMONADE_TOKEN
Questions
No — npx fetches the tool for that one run. There's nothing to install globally and nothing to add to your project.
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.
Yes — add the token as a secret in your CI provider, export it as LEMONADE_TOKEN, and run the same command as a step in your pipeline.
Yes. Run your generator the way you already do, then point --dir at the folder it writes to — that folder is what goes live.
Prefer a different route?
Start from a template, change the words in your browser, press publish.
Connect a repository once. Every push after that puts the new version live.
Just the files, dropped straight into the browser.
Connect the MCP server and ask it to deploy, in plain language.
See what every site includes, or check pricing — 99¢ a month per site, cancel any time.