Setup guide

~20–30 minutes · no command line · you'll need Node.js installed.

Today: Claude → LinkedIn

On this page
Before you start 1 · Run the installer 2 · Your keys 3 · Database 4 · GitHub 5 · Vercel 6 · Go live Troubleshooting Updates Support

Before you start

Free accounts (have these ready, or make them as you go): GitHub, Supabase, Vercel, an Anthropic (Claude) API key, and a LinkedIn developer app. It all runs on free tiers — you only pay your own AI usage (a few cents per post). You also need Node.js installed to run the installer.

1 · Run the installer

Unzip your download into a fresh folder.
Double-click Start Installer.cmd (Windows). macOS: Start Installer.command · Linux: bash start-installer.sh
A guided setup opens in your browser at localhost:4321. Keep that window open while you work.

Nothing leaves your computer. The installer writes a local .env.local and uses your logins — JaloGames never sees your keys or data.

2 · Your keys

Supabase

Project URL — in Supabase, click the top search bar and type "Copy API URL" (it's a bit hidden).
anon + service_role keys — Project Settings → API Keys.

Anthropic (Claude)

API key — Claude Console → Dashboard → Get API Key. Set a small monthly spend cap while you're there.

Create an app at linkedin.com/developers/apps.
Add the products Sign In with LinkedIn (OIDC) + Share on LinkedIn.
Copy the Client ID + Client Secret from the Auth tab.

Paste everything into the installer's Your keys section, then click Save → Test setup. The two secrets are generated for you.

3 · Database

In the installer's Your database card, click Copy schema.sql.
Click Open SQL editor (it deep-links to your project) → paste → Run.
Click Verify database — it should say "schema applied ✓".

4 · GitHub

Important: your token needs both the repo and workflow scopes — JaloCron ships a scheduled GitHub Action, and GitHub blocks pushing it without workflow. The installer's "Create a token" link pre-checks both.

Click Create a token → confirm repo + workflow are checked → Generate → paste it → Connect.
Pick a repository name (any new name) → Create & push.

5 · Vercel

Click Import repo → on Vercel, import the repo you just created and hit Deploy. The first build can fail for missing keys — that's expected.
Back in the installer, paste a Vercel token → Connect → Set env + deploy. It pushes all your settings and deploys to production.

6 · Go live

In the installer's Final links step, paste your live URL — the exact values fill in. Then:

GitHub Actions secrets (turns on the scheduler)

Open the repo's Settings → Secrets and variables → Actions → New repository secret (the green button — Repository secrets, not Environment). Add APP_URL and CRON_SECRET (both shown in the installer). Then open the Actions tab and enable workflows. Click Test scheduler to confirm.

LinkedIn redirect URL

Your LinkedIn app → Auth → Authorized redirect URLs → add the exact URL shown ({your-site}/api/auth/linkedin/callback).

Supabase Auth URLs

Set Site URL to your live URL and add the Redirect (with /**) so magic-link sign-in works in production.

When Test scheduler passes, the big green Open my live app button unlocks. Sign in, fill your profile, Connect LinkedIn, and flip Live posting on when ready (it starts in safe preview mode).

Troubleshooting

Push failed: "without `workflow` scope"

Your GitHub token is missing the workflow scope. Make a new token with repo + workflow both checked, paste it, Connect, and push again.

Magic-link sign-in opens localhost in production

Supabase Site URL is still localhost. Set Site URL + Redirect URLs to your live URL, then request a fresh link.

LinkedIn "redirect_uri does not match"

Add the exact {your-site}/api/auth/linkedin/callback in your LinkedIn app's Auth tab — no trailing slash, https for production.

Scheduled posts don't appear

The scheduler isn't firing. Confirm the Actions secrets + enabled workflows (step 6), or use Run due now in the app. (Locally there's no scheduler.)

"ANTHROPIC_API_KEY is not set" locally

A blank ANTHROPIC_API_KEY in your shell can shadow .env.local. Use a clean terminal. (Never an issue on Vercel.)

Updates

Your purchase includes lifetime updates. When a new version ships (new models, new platforms), re-download the ZIP from your Lemon Squeezy account and copy the files over your project — your .env.local is untouched. Then commit & push, or re-run the installer's deploy step.

Support

Stuck on anything? Email jalo@jalogames.fi — I read every message.