Skip to main content

​
Overview

Once you’ve connected a deployment platform and configured your project, deploying is just one click away.

​
Prerequisites

Before deploying, ensure:
  1. You’ve connected a platform (Netlify or Vercel)
  2. Your project is configured with a deployment target
  3. You have owner access to the project

​
Triggering a Deployment

1

Open Your Project

Navigate to the project you want to deploy
2

Click Deploy

Find and click the Deploy button
3

Monitor Progress

Watch the deployment status as it progresses through stages
4

View Your Site

Once complete, click the deployment URL to see your live site

​
Deployment Stages

A typical deployment goes through these stages:
StageDescription
QueuedDeployment is waiting to start
BuildingRunning build commands (if configured)
DeployingUploading files to the platform
ReadyDeployment complete and live
Build times vary based on your project size and complexity. Most deployments complete within a few minutes.

​
Deployment Success

When a deployment succeeds, you’ll see:
  • Green status indicator
  • Live URL to your deployed site
  • Timestamp of completion
Click the URL to open your site in a new tab.

​
Deployment Failure

If a deployment fails:
  1. Check the error message in VibeHub
  2. Review build logs in your platform dashboard (Netlify/Vercel)
  3. Common issues:
    • Missing dependencies
    • Build command errors
    • Invalid configuration

​
Debugging Failed Deployments

Verify your build command is correct. Check that all dependencies are in package.json and the build works locally.
Ensure all required files are committed. Check .gitignore isn’t excluding necessary files.
Some builds need environment variables. Configure these in your platform’s dashboard.
Very large builds may timeout. Consider optimizing your build process or splitting into smaller chunks.

​
Deployment History

VibeHub tracks all your deployments:
FieldDescription
StatusSuccess, failed, or in progress
PlatformNetlify or Vercel
URLLink to the deployed version
CommitWhich commit was deployed
TimestampWhen it was deployed

​
Viewing History

To see past deployments:
  1. Open your project
  2. Look for the deployment history section
  3. Click any deployment to see details

​
Deploying Specific Commits

Currently, VibeHub deploys the latest code on your selected branch. For deploying specific commits:
  1. Switch to the branch containing the commit
  2. Deploy from that branch

​
Redeploying

To redeploy the same code:
  1. Click Deploy again
  2. A new deployment will start
This is useful for:
  • Retrying after a transient failure
  • Rebuilding with new environment variables
  • Testing platform changes

​
Best Practices

Run your build command locally before deploying to catch errors early.
Deploy feature branches to preview before merging to main.
Keep an eye on deployment times. Increasing times may indicate build issues.
For detailed error information, always check your Netlify/Vercel dashboard.

​
Deployment vs CI/CD

VibeHub deployment is manual and on-demand. For automatic deployments on every push, configure:
  • Netlify: Connect your repo directly in Netlify settings
  • Vercel: Connect your repo directly in Vercel settings
VibeHub deployment is great for:
  • Quick manual deploys
  • Deploying specific branches
  • Testing before setting up full CI/CD

​
Next Steps

Configure Netlify

Fine-tune Netlify settings

Configure Vercel

Fine-tune Vercel settings