CLI sets up your project on first deploy

You can run easel deploy or easel link in a folder that isn’t linked yet, and the CLI sets up the project for you. It matches how vercel behaves on first run: no dashboard visit needed.

Sign in and pick a project

If you’re not signed in, the CLI opens your browser to sign in first. When you belong to more than one workspace, it asks Which workspace?. Then it looks for a project with the same name as the folder:

Set up "~/code/storefront"
? Found project "acme/storefront". Link to it? [Y/n]

If nothing matches, you can link an existing project by name or create a new one.

Create with detected settings

For a new project, the CLI detects your framework and shows the build settings it will use. Answer y to Customize settings? to change the Build Command, Output Directory, or Install Command:

? Link to existing project? [y/N] n
? Name? (storefront)
Detected Next.js (Build Command: next build, Output Directory: .next)
? Customize settings? [y/N]
Linked acme/storefront (saved to .easel/project.json)

The link is saved to .easel/project.json, so later commands in that folder skip setup.

First deploy goes to production

The first easel deploy of a new project goes to production. Later deploys create previews unless you pass --prod. Pass --yes to accept every default without prompts, for example in a script.

See Deploy from the CLI.