deploy-vercel-render
Skill2 starsChanged 4 months agoMITView on GitHub
Deploy vpeetla-ai demos: Vercel static/Next.js frontends, Render FastAPI backends, env vars, free tier gotchas. Use when shipping demos, fixing deploy failures, or adding render.yaml / vercel.json.
- Reads credentials
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 29
Never commit secrets — Render dashboard only
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Deploy: Vercel + Render
Standard split
| Layer | Host | Config |
| UI demo | Vercel | vercel.json, config.js API URL |
| Python API | Render | render.yaml, Dockerfile |
Render free tier
# render.yaml
plan: free # REQUIRED — avoids credit card promptEnv vars (Render)
GROQ_API_KEY,GITHUB_TOKEN(LoopForge)AEGISAI_API_BASE_URL(gateway integrations)- Never commit secrets — Render dashboard only
Vercel
- Deploy from subfolder:
cd demo && vercel --prod - Point
LOOPFORGE_API/API_BASEinconfig.jsto Render URL
Health checks
curl https://loopforge-api.onrender.com/healthCold start
- Render free spins down ~15min idle — document in README
- Vercel edge is always warm for static
Reference deploys
| Project | Demo | API |
| LoopForge | demo-omega-taupe.vercel.app | loopforge-api.onrender.com |
| Enterprise RAG | enterprise-rag-platform.vercel.app | — |
| VAP | venkat-ai-platform.vercel.app | — |
Docs
Each repo: docs/DEPLOY.md with exact commands and env table
Other versions4 projects use a version of this.
Word for word · 4
- vpeetla-ai/aegisai-enterprise-agent-platform★ 2100% same
- vpeetla-ai/multi-agent-system-pattern★ 2100% same
- vpeetla-ai/reflection-agent-pattern★ 2100% same
- vpeetla-ai/swarm-agent-pattern★ 2100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- aegis-gatewaySkill
- agentic-engineeringSkill
- governed-ai-stackSkill
- grill-with-contextSkill
- hitl-side-effectsSkill
- langgraph-orchestrationSkill
- loop-engineeringSkill
- portfolio-adrSkill
- rag-governanceSkill
- repo-fix-prSkill
- setup-vpeetla-skillsSkill
- tdd-agent-loopsSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.