Deploying Projects from Vercel CLI
The command is used to deploy Vercel Projects and can be used from either the root of the Vercel Project directory or by providing a path.
Deploys the current Vercel project, when run from the Vercel Project root.
You can alternatively use the command for the same effect, if you want to be more explicit.
Deploys the Vercel project found at the provided path, when it's a Vercel Project root.
When deploying, stdout is always the Deployment URL.
Writes the Deployment URL output from the deploy
command to a text file.
By default, when you promote a deployment to production, your domain will point to that deployment. If you want to create a production deployment without assigning it to your domain, for example to avoid sending all of your traffic to it, you can:
- Turn off the auto-assignment of domains for the current production deployment:
- When you are ready, manually promote the staged deployment to production:
You can build Vercel projects locally to inspect the build outputs before they are deployed. This is a great option for producing builds for Vercel that do not share your source code with the platform.
It's also useful for debugging build outputs.
Using the vercel command to deploy and write stdout
to a text file.
This produces in the Build Output API format. You can review the output, then deploy with:
Deploy the build outputs in .vercel/output produced
by vercel build.
Review the When not to use --prebuilt section to understand when you should not use the flag.
See more details at Build Output API.
Was this helpful?