← All guides
Claude Code deployment rescue
Claude Code app works locally but will not deploy
Claude CodeVPSSupabase
Short answer
The Claude Code-built app running on your production server with correct dependencies, build config, and live URL.
Why this matters
The app runs perfectly on your machine after Claude Code built it, but the server fails with missing modules, wrong Node version, or build errors.
Walkthrough
- 01
Audit what Claude Code produced
Claude Code generates code but may not set up production build and deploy config.
- Check package.json for build and start scripts.
- Confirm the Node version matches what the app expects.
- List every environment variable the app reads from process.env.
- 02
Set up the production server
The server needs dependencies, env vars, and a process manager.
- Install all dependencies with the same package manager used locally.
- Add environment variables to the server deploy panel.
- Set up a process manager to keep the app alive.
- 03
Build, deploy, and test
Run the production build and verify every integration works.
- Build the app on the server with production env vars loaded.
- Start the process and confirm it responds on the expected port.
- Test database connections, auth, and any external API calls.
Where RepoAssistant fits
RepoAssistant takes Claude Code-built apps from local-only to production servers with domain, database, and handover.