Hi! I'm Primordia. Ask me anything, or click the ✏️ button in the top right to propose a change to this app.
Most recent change:
Add deploy-to-exe.dev command
# Add deploy-to-exe.dev command
## What changed
Added
bun run deploy-to-exe.dev <server-name> command that deploys Primordia to an exe.dev server in a single step.
New files:
- scripts/deploy-to-exe-dev.sh — the deploy script
- New "deploy-to-exe.dev" entry in package.json scripts
## How it works
Running bun run deploy-to-exe.dev primordia connects via SSH to primordia.exe.xyz and:
1. Copies .env.local (secrets) from the local machine to the server via scp
2. Installs git and bun on the server if they are not already present
3. Clones the GitHub repo (or pulls the latest main if already cloned)
4. Runs bun install to install dependencies
5. Starts bun run dev with HOSTNAME=0.0.0.0 so the app is publicly reachable at http://<server-name>.exe.xyz:3000
6. Waits for the Next.js "Ready" signal and tails the logs
Because the server runs next dev (NODE_ENV=development), the fast local evolve flow is active — change requests are handled directly by the Claude Agent SDK + git worktrees on the remote machine, with no GitHub Issues / Actions / Vercel round-trip required.
## Why
The GitHub → Actions → Vercel pipeline works but is slow (minutes per change). The local dev flow (Claude Agent SDK + git worktrees) is much faster but requires installing git, bun, and Claude Code locally. Deploying the dev server to an exe.dev instance gives users the speed of the local flow with zero local prerequisites — just SSH access and a .env.local file.