What you need
Deploylet currently accepts a static output folder. Remote deployments require a Deploylet token and default tohttps://api.deploylet.com.
Initialize a project
$ node packages/cli/dist/index.js init launch-preview --dir ./launch-preview --yes
$ node packages/cli/dist/index.js config --config ./launch-preview/deploylet.config.jsonThe generated deploylet.config.json names the space, output directory, environment, and requested runtime capabilities. Keep the output inside the configuration directory.
Inspect before publishing
$ node packages/cli/dist/index.js deploy ./launch-preview/dist \
--config ./launch-preview/deploylet.config.json --dry-runThe dry run builds a manifest locally. It does not upload files. Deployment manifests exclude common local secret files and source maps by default.
Publish
$ DEPLOYLET_TOKEN=dl_live_... node packages/cli/dist/index.js deploy ./launch-preview/dist \
--config ./launch-preview/deploylet.config.jsonThe current single-request upload path is capped at 40 files. Use the beta channel when your build exceeds that limit or needs a workflow that is not listed here.