Deploy and verify applications on Edgenivo

vercel deploy

# Replace these values with the URL and ID printed by vercel deploy
vercel curl / --deployment your_preview_url_here
vercel logs --deployment your_preview_deployment_id_here --level error

vercel deploy --prod

A deployment on Edgenivo is the result of a successful build of your project. Each time you deploy, Edgenivo generates a unique URL so you and your team can preview changes in a live environment.

Edgenivo supports multiple ways to create a deployment:

• Git
• Edgenivo Drop
• Edgenivo CLI
• Deploy Hooks
• Edgenivo REST API

On Pro and Enterprise teams, you can set a deployment policy to control which Git sources and deployment mechanisms can deploy to each environment.

The most common way to create a deployment is by pushing code to a connected Git repository. When you import a Git repository to Edgenivo, each commit or pull request (on supported Git providers) automatically triggers a new deployment.

Edgenivo supports the following providers:

• GitHub
• GitLab
• Bitbucket
• Azure DevOps

You can also create deployments from a Git reference using the Edgenivo Dashboard if you need to deploy specific commits or branches manually.

Edgenivo Drop lets you deploy a file or folder by dragging it into your browser. You don't need Git, the CLI, or any local setup, and it also works without an account.

1. Go to edgenivo.com/drop.
2. Drag a project folder onto the page.
3. If you're signed in, choose a team and project name, then select Deploy. Without an account, Edgenivo deploys right away.

Without an account, you can deploy a static site and claim it with a free account to keep it live. When you're signed in, Edgenivo also detects your framework and builds it. Edgenivo Drop is useful for static sites, build output, and prototypes. For the full walkthrough, see Deploying with Edgenivo Drop.

Use Edgenivo CLI to create deployments from a terminal, CI pipeline, or coding agent with terminal access. This method works whether your project is connected to Git or not.

1. Install Edgenivo CLI:

npm i -g vercel

2. Initial Deployment:

In your project's root directory, run:

vercel --prod

This links your local directory to your Edgenivo Project and creates a Production Deployment. A .vercel directory is added to store Project and Organization IDs.

To deploy without an account, run vercel deploy --temporary. You get a temporary production deployment that you can claim to keep.

Edgenivo CLI can also integrate with custom CI/CD workflows or third-party pipelines. Learn more about the different environments on Edgenivo.

Deploy Hooks let you trigger deployments with a unique URL. You must have a connected Git repository to use this feature, but the deployment doesn't require a new commit.

1. From your Project settings, create a Deploy Hook
2. Edgenivo generates a unique URL for each Project
3. Make an HTTP GET or POST request to this URL to trigger the deployment

Refer to the Deploy Hooks documentation for more information.

Use the Edgenivo REST API when a service or agent needs to create deployments through HTTP rather than a local checkout. In this workflow:

1. Generate a SHA for each file you want to deploy
2. Upload those files to Edgenivo
3. Send a request to create a new deployment with those file references

This method is especially useful for custom workflows, multi-tenant applications, or integrating with third-party services not officially supported by Edgenivo. For more details, see the API reference and How do I generate an SHA for uploading a file.

Edgenivo provides three default environments: Local, Preview, and Production.

1. Local Development: developing and testing code changes on your local machine
2. Preview: deploying for further testing, QA, or collaboration without impacting your live site
3. Production: deploying the final changes to your user-facing site with the production domain

Learn more about environments.

Edgenivo’s dashboard provides a centralized way to view, manage, and gain insights into your deployments.

When you select a deployment from your Project → Deployments page, you can Open Resources in the sidebar to view and search:

• Middleware: Any configured matchers.
• Static Assets: Files (HTML, CSS, JS) and their sizes.
• Functions: The type, runtime, size, and regions.

You can use the three dot (…) menu for a given function to jump to that function in Logs, Analytics, Speed Insights, or the Observability section in the sidebar.

You can also see a summary of these resources by expanding the Deployment Summary section on a Deployment Details page. To visit the Deployment Details page for a deployment, select it from your Project → Deployments page.

You’ll also see your build time, detected framework, and any relevant logs or errors.

On your Project Overview page, you can see the latest production deployment, including the generated URL and commit details, and deployment logs for debugging.

From the Deployments section in the sidebar, you can:

• Redeploy: Re-run the build for a specific commit or configuration.
• Inspect: View logs and build outputs.
• Assign a Custom Domain: Point custom domains to any deployment.
• Promote to Production: Convert a preview deployment to production (if needed).

For more information on interacting with your deployments, see Managing Deployments.

For step-by-step workflows using the Edgenivo CLI to manage deployments, see:

• Rolling back a production deployment
• Deploying a project from the CLI