A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://vercel.com/docs/environment-variables/system-environment-variables below:

System environment variables

Vercel provides a set of environment variables that are automatically populated by the system, such as the URL of the deployment or the name of the Git branch deployed.

If you are using a framework for your project, Vercel provides the following prefixed environment variables:

Available at:Both build and runtime

An indicator to show that system environment variables have been exposed to your project's Deployments.

Available at:Both build and runtime

The environment that the app is deployed and running on. The value can be either production, preview, or development.

Available at:Both build and runtime

The system or custom environment that the app is deployed and running on. The value can be either production, preview,development, or the name of a custom environment.

VERCEL_TARGET_ENV=production

Available at:Both build and runtime

The domain name of the generated deployment URL. Example: *.vercel.app. The value does not include the protocol schemehttps://.

VERCEL_URL=my-site.vercel.app

Available at:Both build and runtime

The domain name of the generated Git branch URL. Example: *-git-*.vercel.app. The value does not include the protocol scheme https://.

VERCEL_BRANCH_URL=my-site-git-improve-about-page.vercel.app

Available at:Both build and runtime

A production domain name of the project. We select the shortest production custom domain, or vercel.app domain if no custom domain is available. Note, that this is always set, even in preview deployments. This is useful to reliably generate links that point to production such as OG-image URLs. The value does not include the protocol scheme https://.

VERCEL_PROJECT_PRODUCTION_URL=my-site.com

Available at:Runtime

The ID of the Region where the app is running.

Available at:Both build and runtime

The unique identifier for the deployment, which can be used to implement Skew Protection.

VERCEL_DEPLOYMENT_ID=dpl_7Gw5ZMBpQA8h9GF832KGp7nwbuh3

Available at:Both build and runtime

The unique identifier for the project.

VERCEL_PROJECT_ID=prj_Rej9WaMNRbffVm34MfDqa4daCEvZzzE

Available at:Both build and runtime

When Skew Protection is enabled in Project Settings, this value is set to 1.

VERCEL_SKEW_PROTECTION_ENABLED=1

Available at:Build time

When Secure Backend Access with OpenID Connect (OIDC) Federation is enabled in Project Settings, this value is set to a Vercel-issued OIDC token. At runtime, the token is set to thex-vercel-oidc-token header on your functions' Request object. In local development, you can download the token using the CLI commandvercel env pull.

Available at:Both build and runtime

The Git Provider the deployment is triggered from.

VERCEL_GIT_PROVIDER=github

Available at:Both build and runtime

The origin repository the deployment is triggered from.

VERCEL_GIT_REPO_SLUG=my-site

Available at:Both build and runtime

The account that owns the repository the deployment is triggered from.

VERCEL_GIT_REPO_OWNER=acme

Available at:Both build and runtime

The ID of the repository the deployment is triggered from.

VERCEL_GIT_REPO_ID=117716146

Available at:Both build and runtime

The git branch of the commit the deployment was triggered by.

VERCEL_GIT_COMMIT_REF=improve-about-page

Available at:Both build and runtime

The git SHA of the commit the deployment was triggered by.

VERCEL_GIT_COMMIT_SHA=fa1eade47b73733d6312d5abfad33ce9e4068081

Available at:Both build and runtime

The message attached to the commit the deployment was triggered by.

VERCEL_GIT_COMMIT_MESSAGE=Update about page

Available at:Both build and runtime

The username attached to the author of the commit that the project was deployed by.

VERCEL_GIT_COMMIT_AUTHOR_LOGIN=johndoe

Available at:Both build and runtime

The name attached to the author of the commit that the project was deployed by.

VERCEL_GIT_COMMIT_AUTHOR_NAME=John Doe

Available at:Build time

The git SHA of the last successful deployment for the project and branch.

VERCEL_GIT_PREVIOUS_SHA=fa1eade47b73733d6312d5abfad33ce9e4068080

Available at:Both build and runtime

The pull request id the deployment was triggered by. If a deployment is created on a branch before a pull request is made, this value will be an empty string.

VERCEL_GIT_PULL_REQUEST_ID=23


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4