← Back to libraryShip it
Deploy to production
It runs locally - now put it on the public internet
The prompt
I want to deploy my project. Give me steps I can follow literally. Project: - Type: {{e.g. Next.js full-stack / static site / Python API}} - Code lives at: {{e.g. GitHub repo}} - Server or database: {{yes / no}} - Budget: {{free tier preferred, or paid is fine}} - My experience: {{e.g. I write code but have never configured a server}} Please: 1. Recommend 1-2 suitable platforms and say why. Do not list ten for me to choose from. 2. Give the full path from zero to a live URL - where to click and what to fill in. 3. List required environment variables or secrets and how to set them on the platform. 4. How to verify after deploy: which URL, which logs. 5. The classic first-deploy traps: build failures, missing env vars, wrong paths. Rules: - Pitch it at my experience level. Do not assume I know nginx, Docker or CI. - If a step may be stale because the platform UI changed, tell me to trust the official docs.
Replace the {{}} parts with your own content
Why it works
- Stating budget and experience stops AI from handing you a plan that needs an ops engineer
- One or two recommendations instead of ten lowers the choice cost - platforms are similar enough that finishing one matters more
- Listing env vars separately targets the top deploy failure: works locally, missing in production
- Flagging possibly-stale UI steps saves you hunting for buttons that no longer exist
What it looks like
Deploying a Next.js site, AI suggests Vercel or self-hosting, walks repo connect, env vars, build, domain, and notes config differences like output: standalone.
Where it bites
- Not saying whether there is a server, so you get a static host that cannot run your API
- Missing env vars: fine locally, blank page in production, with no obvious cause