CLI Reference
Usage
npx luvabase@latest <command> [options]
# Or install globally
npm install -g luvabase
luvabase <command> [options]Summary
| Global Option | Description |
|---|---|
-V, --version | Output the version number. |
-h, --help | Display help for command. |
| Command | Description |
|---|---|
init [options] | Create a luvabase.jsonc manifest in the current directory. |
bundle [options] | Create a normalized .luva app bundle in .luvabase/. |
deploy [options] | Bundle the current project and deploy it to the cloud, or deploy an existing .luva bundle. |
whoami | Show the authenticated Luvabase user. |
Command Reference
init
Create a luvabase.jsonc manifest in the current directory.
| Option | Description |
|---|---|
-i, --identifier <identifier> | Set the app identifier. |
-n, --name <name> | Set the app name. |
-y, --yes | Use default values without prompting. |
-h, --help | Display help for command. |
bundle
Create a normalized .luva app bundle in .luvabase/.
| Option | Description |
|---|---|
-o, --outfile <path> | Write the bundle to this file. Defaults to .luvabase/app.luva. |
-m, --manifest <path> | Path to luvabase.jsonc. |
--build-command <command> | Custom build command to run before bundling. |
--skip-build | Skip the project build step. |
--wrangler-config <path> | Path to wrangler.jsonc or wrangler.json. |
-h, --help | Display help for command. |
deploy
Deploy the app to Luvabase. It will either create or update a pod depending on if one is found on the target account.
| Option | Description |
|---|---|
--publish | Publish the app in addition to deploying it. |
-b, --bundle <path> | Path to an existing .luva app bundle to deploy (created with bundle command). If not selected bundling will be done first. |
-a, --account <id> | Target account id. |
--no-wait | Return after queueing pods instead of waiting. |
-h, --help | Display help for command. |
whoami
Show the authenticated Luvabase user.
Prints a preview of the stored API token and the authenticated user.
npx luvabase@latest whoami