A deployment is the result of building your Project and making it available through a live URL.
This section contains information about making, managing, and understanding the behavior of deployments.
Deployments can be made with Vercel via the following:
When using these integrations, every push to a branch will provide you with a preview deployment to view your changes.
Use cases for Deploy Hooks include:
- Rebuilding your site to reflect changes in a Headless CMS
- Scheduling deployments with Cron Jobs
To create a Deploy Hook, visit the settings page of your Project where you can choose the branch to deploy when the HTTP endpoint receives a POST request.
You can find more information about Deploy Hooks in the documentation.
To make a preview deployment, use the
To make a production deployment, use the
vercel --prod command:
The Vercel API can be used to make deployments by making an HTTP POST request to the relevant endpoint, including the files you wish to deploy as the body.
You can find more information about the Vercel API in the API Reference.
The Vercel Dashboard is the easiest way for you to manage your deployments.
Through the Vercel Dashboard, you can find a variety of settings; including a Domains tab where you can add custom domains to your Project.
You can filter and sort your deployments based on branch and status. Go to the Deployments tab inside your Project dashboard. A drop-down for Status sorts the deployments according to the desired status code.
These are the following Status values:
- Ready: A successful deployment
- Error: An unsuccessful or failed deployment
- Building: A deployment currently being built
- Queued: A deployment waiting to be built
- Canceled: A deployment that was canceled
You will also find a drop-down search menu with a placeholder text for "All Branches". This helps you select any deployed branch from the drop-down or filter by typing in the search box.
The three types of logs available are, Build Time, Runtime, and Edge Network.
Build Time logs are generated during the build step. These logs contain information about the build process and are stored indefinitely.
Edge Network logs are generated when requesting a path from the Edge. These logs contain information about a request to a specific path with details such as the path name, request method, and status code. These logs are not persisted.
Runtime logs are generated by Serverless Functions while they're being invoked. Runtime logs are stored in memory only as they arrive from the Serverless Function and are not persisted.
The only exception to this are failed requests. If a request leads to the Serverless Function throwing an error, the log for this will be stored indefinitely whereas all other Runtime logs will be lost when navigating away from the page.
The maximum size limit of each log is 4kb. If the size of the log exceeds this, only the last 4kb of data to arrive will be shown.
All deployment URLs have two special pathnames:
/_logs to a deployment URL or custom domain, you will be able to see a realtime stream of logs from your deployment build processes and serverless invocations.
These pathnames redirect to
https://vercel.com and require logging in to access any sensitive information. By default, a 3rd-party can never access your source or logs by crafting a deployment URL with one of these paths.
However, you can configure project settings to make these paths public. Learn more here.