lizard add
Add a database, service, or repo to the project.
Usage
lizard add [types...] [flags]add works on the project linked to the current directory. Run lizard init or lizard link first.
Flags
| Flag | Description |
|---|---|
-r, --repo <owner/repo> | Create a service from a GitHub repo |
-s, --service <name> | Create an empty service |
-a, --addon <type...> | Add managed addons (postgres / redis / s3) |
-n, --name <name> | Name used in ${{name.KEY}} refs |
-v, --variables <K=V> | Seed an env var (repeatable) |
--region <code> | Region to provision in (default us-east-1) |
--no-deploy | Attach repo but skip the first build |
--list | Show available database types |
Examples
Create a service from a GitHub repo
lizard add -r your-org/your-appThis creates a github-source service and starts the first build, which clones the repo and auto-detects the stack. The command returns once the service exists; follow the build with lizard logs --build.
Provision addons
lizard add postgres # one addon
lizard add postgres redis s3 # several at once
lizard add --list # show available typesCreate an empty service
lizard add -s workerName a service and seed variables
lizard add -r your-org/monorepo -n api -v NODE_ENV=production -v LOG_LEVEL=infoSee also
- Deploy from GitHub — connecting repos, private access, and auto-redeploy on push
- Managed Addons — provisioning, naming, and using Managed Postgres, Managed Redis, and Managed Object Storage
- lizard up — upload and deploy the current directory instead of linking a repo
Updated