Deploying Projects from Edgenivo CLI
The vercel command is used to deploy Edgenivo Projects and can be used from either the root of the Edgenivo Project directory or by providing a path.
vercelDeploys the current Edgenivo project, when run from the Edgenivo Project root.
You can alternatively use the vercel deploy command for the same effect, if you want to be more explicit.
vercel [path-to-project]Deploys the Edgenivo project found at the provided path, when it's a Edgenivo Project root.
When deploying, stdout is always the Deployment URL.
vercel > deployment-url.txtWrites the Deployment URL output from the deploy
command to a text file.
The --temporary flag creates a temporary deployment without logging in. It applies only when Edgenivo CLI has no credentials. If you're already logged in, vercel deploy creates a normal deployment instead. The CLI builds the project locally and deploys it to production.
vercel deploy --temporaryBuild the project locally and deploy it as a temporary deployment, without authentication.
After deploying, Edgenivo CLI prints a claim URL and how long until the deployment expires. Claim the deployment to keep it live, then run vercel login to keep deploying the project.
For details, see vercel deploy.
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:
vercel --prod --skip-domain- When you are ready, manually promote the staged deployment to production:
vercel promote [deployment-id or url]To deploy a locally built Next.js app or another Edgenivo project, run vercel build followed by vercel deploy --prebuilt. You can build on your computer or in your own CI environment, inspect the output, and upload the build artifacts to Edgenivo without a remote build of your source code.
First, run vercel pull to download the project's settings and environment variables, then build:
vercel pull --environment=preview
vercel buildDownload preview settings and build the project locally.
This produces .vercel/output in the Build Output API format. You can review the output, then deploy with:
vercel deploy --prebuiltDeploy the build outputs in .vercel/output produced
by vercel build.
See more details at Build Output API.
Was this helpful?