Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/fmoraga01/SpinAI/llms.txt

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

SpinAI is built on Next.js 16 and deploys to Vercel with zero configuration beyond supplying the required environment variables. Vercel auto-detects the framework, handles the build pipeline, and provides a globally distributed edge network — making it the natural home for an internal team tool that needs to be reliably available every Friday.
1

Push your fork to GitHub

Make sure your fork of the SpinAI repository is pushed to GitHub and accessible from your Vercel account.
git push origin main
2

Import the repository in Vercel

Go to vercel.com, click Add New → Project, and select Import Git Repository. Choose your SpinAI fork from the list.
3

Confirm the framework preset

Vercel automatically detects Next.js as the framework. No changes to the build settings are required — the default preset works as-is.
4

Add environment variables

Before deploying, expand the Environment Variables section in the Vercel dashboard and add each of the following key-value pairs:
VariableDescription
NEXT_PUBLIC_SUPABASE_URLYour Supabase project URL
NEXT_PUBLIC_SUPABASE_ANON_KEYYour Supabase anonymous (public) API key
PINThe numeric PIN used to protect the app
JWT_SECRETSecret key used to sign the HttpOnly session cookie
GMAIL_USERGmail address used by Nodemailer to send notifications
GMAIL_PASSGmail app password for the above account
CRON_SECRETShared secret that authorises GitHub Actions cron requests
All variables are required. The app will not start correctly if any are missing.
5

Click Deploy

Click the Deploy button. Vercel runs npm run build (the standard Next.js build command — no custom configuration is needed) and publishes the app. The first deploy typically completes in under two minutes.
6

Copy your production URL

Once the deployment succeeds, copy your production URL (e.g. https://spinai.vercel.app). You will need this URL when configuring GitHub Actions so the cron jobs know where to send requests.

Build command and output

SpinAI uses the standard Next.js build pipeline with no custom configuration in next.config.ts. Vercel resolves the build command automatically:
npm run build
The output directory is .next, which Vercel also detects automatically. There is no need to change either setting in the Vercel project configuration.
Enable Vercel Preview Deployments to automatically deploy every pull request to an isolated preview URL. This lets you verify UI changes, test environment variable updates, and review new features in a live environment before merging to main — without touching the production deployment.
The CRON_SECRET value must be identical in both your Vercel environment variables and your GitHub Actions repository secrets. If they differ, all automated cron requests will be rejected with a 401 Unauthorized response and no notifications or news refreshes will fire.
The free Vercel Hobby tier is fully sufficient for an internal team tool. SpinAI’s traffic profile — a handful of team members plus two scheduled cron calls per day — fits comfortably within the free tier’s bandwidth and function execution limits.
Once your app is live on Vercel, proceed to GitHub Actions to configure the automated weekly notification and AI news feed refresh workflows.

Build docs developers (and LLMs) love