Deployment

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/kiwigaze/omnisearches/llms.txt

Use this file to discover all available pages before exploring further.

​

Overview

​

Prerequisites

• A Google API key with Gemini API access
• An OpenRouter API key with Deepseek model access
• A GitHub account (for most deployment options)
• Node.js v18 or higher installed locally

​

Deploy to Railway

​

One-Click Deployment

1. Click the Deploy on Railway button
2. Log in with your GitHub account
3. Configure your environment variables:
   • GOOGLE_API_KEY
   • REASON_MODEL_API_KEY
   • REASON_MODEL_API_URL
   • REASON_MODEL (optional)
4. Click Deploy

​

Manual Railway Deployment

1. Install Railway CLI:

npm install -g @railway/cli

2. Login to Railway:

railway login

3. Initialize a new project:

railway init

4. Set environment variables:

railway variables set GOOGLE_API_KEY=your_key_here
railway variables set REASON_MODEL_API_KEY=your_key_here
railway variables set REASON_MODEL_API_URL=https://openrouter.ai/api/v1
railway variables set REASON_MODEL=deepseek/deepseek-r1-distill-llama-70b:free
railway variables set NODE_ENV=production

5. Deploy:

railway up

​

Railway Configuration

• Build command: npm run build
• Start command: npm run start

1. Installs dependencies (npm install)
2. Builds the frontend with Vite
3. Bundles the backend with esbuild
4. Outputs to the dist/ directory

​

Deploy to Vercel

​

Deployment Steps

1. Install Vercel CLI:

npm install -g vercel

2. Login:

vercel login

3. Deploy:

vercel

4. Set environment variables in the Vercel dashboard:
   • Go to Project Settings → Environment Variables
   • Add all required environment variables
   • Redeploy to apply changes

​

Vercel Configuration

{
  "buildCommand": "npm run build",
  "outputDirectory": "dist/client",
  "framework": "vite",
  "rewrites": [
    {
      "source": "/(.*)",
      "destination": "/"
    }
  ]
}

​

Deploy with Docker

​

Create Dockerfile

FROM node:18-alpine

# Set working directory
WORKDIR /app

# Copy package files
COPY package*.json ./

# Install dependencies
RUN npm ci --only=production

# Copy application files
COPY . .

# Build application
RUN npm run build

# Expose port
EXPOSE 3000

# Set environment to production
ENV NODE_ENV=production

# Start application
CMD ["npm", "start"]

​

Build and Run

# Build Docker image
docker build -t omnisearches .

# Run container with environment variables
docker run -p 3000:3000 \
  -e GOOGLE_API_KEY=your_key \
  -e REASON_MODEL_API_KEY=your_key \
  -e REASON_MODEL_API_URL=https://openrouter.ai/api/v1 \
  -e REASON_MODEL=deepseek/deepseek-r1-distill-llama-70b:free \
  -e NODE_ENV=production \
  omnisearches

docker run -p 3000:3000 --env-file .env omnisearches

​

Deploy to Heroku

1. Install Heroku CLI:

npm install -g heroku

2. Login and create app:

heroku login
heroku create omnisearches-app

3. Set environment variables:

heroku config:set GOOGLE_API_KEY=your_key
heroku config:set REASON_MODEL_API_KEY=your_key
heroku config:set REASON_MODEL_API_URL=https://openrouter.ai/api/v1
heroku config:set REASON_MODEL=deepseek/deepseek-r1-distill-llama-70b:free
heroku config:set NODE_ENV=production

4. Deploy:

git push heroku main

​

Heroku Configuration

web: npm start

​

Deploy to DigitalOcean App Platform

1. Connect your GitHub repository to DigitalOcean
2. Configure the build settings:
   • Build Command: npm run build
   • Run Command: npm start
3. Set environment variables in the App Platform console
4. Deploy

​

Environment-Specific Deployment Notes

​

Production Checklist

​

Build Commands Reference

​

Post-Deployment

1. Test the application:
   • Visit your deployment URL
   • Try a search query
   • Test reasoning mode
   • Check image search functionality
2. Monitor API usage:
   • Check Google Cloud Console for Gemini API usage
   • Monitor OpenRouter dashboard for credits
3. Set up monitoring:
   • Configure uptime monitoring
   • Set up error tracking (e.g., Sentry)
   • Enable API usage alerts

​

Troubleshooting

​

Build Failures

• Check Node.js version (requires v18+)
• Verify all dependencies are listed in package.json
• Review build logs for specific errors
• Ensure TypeScript compilation succeeds locally

​

Runtime Errors

• Verify all required environment variables are set
• Check that NODE_ENV is set to production
• Review application logs in your hosting platform
• Ensure API keys are valid and active

​

API Errors

• Verify API keys have proper permissions
• Check API quotas and rate limits
• Test API keys locally first
• Review error messages in browser console

​

Continuous Deployment

1. Connect your GitHub repository to your hosting platform
2. Configure automatic deployments from the main branch
3. Push changes to GitHub to trigger deployments

# Make changes locally
git add .
git commit -m "Your changes"
git push origin main

# Deployment happens automatically

​

Scaling Considerations

• Railway: Automatically scales within plan limits
• Vercel: Scales automatically with serverless architecture
• Docker: Use container orchestration (Kubernetes, Docker Swarm)
• Load balancing: Add a reverse proxy (nginx, Caddy) for multiple instances