Schedule For You

Post scheduler: write once, publish to ten social platforms from one queue. Next.js 16 on Vercel Pro, Neon Postgres for data, Neon Auth for sign-in, Vercel Cron for publishing, Neon Object Storage for media.

Route	What it is
/	Landing page, server-rendered. Phones get the mobile design (LandingMobile, chosen by user agent, then kept in step with the viewport); /?desktop=1 shows the full one
/signup, /login	Email + password accounts (Neon Auth)
/app	The dashboard on your real data (signed in)
/demo	The same dashboard with sample data, nothing saved
/app/automations	Signature, RSS auto-post, webhooks (workspace menu → Automations)
/p/<token>	Client preview link: view a post, approve, ask for changes or comment (no account)
/c/<token>	Shared calendar: read-only schedule for clients and teammates; /c/<token>/feed.ics is the iCal feed
/brand	Logo sheet
/api/v1/*	REST API (session or Authorization: Bearer sfy_… API key)
/api/cron/publish	Publishing job, run by Vercel Cron every minute

On phones the dashboard switches to a top bar, a bottom tab bar and a slide-in menu.

How publishing works

1. A post is saved in Postgres with one target per social account.
2. Every minute Vercel Cron calls /api/cron/publish (with CRON_SECRET). It claims due posts with FOR UPDATE SKIP LOCKED, so overlapping runs never post twice.
3. Each target is published through its platform adapter (lib/server/adapters). Media is read from the storage bucket. Tokens are refreshed when close to expiry.
4. Failures retry up to 3 times, 2 minutes apart. Auth errors mark the account "Reconnect needed". Repeating (weekly/monthly) and evergreen posts get their next copy scheduled after publishing.
5. Posts waiting for approval and workspaces with a paused queue are skipped.
6. The same run sends reminder and digest emails, checks RSS feeds (with a time budget so the function never overruns its limit) and removes stale rows (uploads that never finished, abandoned OAuth handshakes, long-expired preview links).

"Publish now" in the dashboard publishes immediately in the request instead of waiting for the cron.

Setup on Vercel

1. Neon: in the Vercel project, add the Neon integration (Storage → Neon). It sets DATABASE_URL and DATABASE_URL_UNPOOLED. Migrations run automatically on every build (scripts/migrate.mjs).
2. Neon Auth (sign-in): neon.ts declares auth: true. Add NEON_AUTH_BASE_URL (the branch's Auth URL from the Neon Console → Auth, e.g. https://ep-….neonauth.c-6.us-east-2.aws.neon.tech/neondb/auth) and NEON_AUTH_COOKIE_SECRET (openssl rand -base64 32). Neon Auth only accepts sign-ins from trusted domains: add your production domain (and any preview domain you use) in the Neon Console → Auth → Domains, or with neon neon-auth domain add https://your-domain.com. Localhost is allowed by default.

This is the beginning of the README. Read the rest at the original. Read the full README ↗