FORJEX
Skip to documentation
Deploy to Vercel

Build & ship

Deploy to Vercel

Deploy a frontend and understand deployment status.

On this page

Before deploying

This path is for Next.js, React/Vite, and Vue/Vite applications. Confirm the production build works locally, then connect your GitHub and Vercel accounts.

Python, Go, and Rust starters need a host that supports their runtime. The starter guides show their local run and build commands.

Deploy from the CLI

1

Open repository setup

From your application folder
forjex forge

Choose the existing-project path if you have already generated your app.

2

Enable Vercel deployment

Select your GitHub destination, choose whether to add CI/CD, and enable deployment when asked. Follow the Vercel authentication prompts.

3

Review the result

Open the deployment URL reported by the provider and check the actual application. If deployment fails, inspect the Vercel build logs before retrying.

Deploy from the browser wizard

In the Forge Wizard, connect your credentials, select a frontend template, and enable Vercel. Forjex links the repository to the Vercel project and checks the latest production deployment.

The dashboard shows a live URL only when the provider confirms a READY deployment. Creating a Vercel project alone does not mean your application is live.

Understand deployment status

  • Ready: the provider confirms a completed deployment.
  • Queued or building: wait and refresh the status.
  • Failed or canceled: inspect the provider logs and retry after fixing the cause.
  • Pending setup or unknown: check the linked repository, credentials, and provider configuration.

Future updates

When the GitHub integration is connected, pushes can trigger Vercel deployments. Verify the integration, production branch, environment variables, and build settings in Vercel. A local build can pass while deployment fails because the environments differ.