Feature Request
"Add a 'boring baseline' app template (auth/rbac + db + crud) so people can go from infra → real app faster"
— u/Few-Garlic2725 on r/vibecoding
Problem
Right now RemoteVibeServer gets you from zero to a working dev environment very fast — but the first thing most users do is still bootstrap a new app from scratch. That means setting up auth, a database schema, RBAC, and basic CRUD before you can start vibing on the actual product.
Proposed Solution
Add an optional starter app template that gets deployed into the Coder workspace automatically, controlled by a config flag in the configurator.
Config flag (proposed)
In cloud-init.yaml / configurator:
STARTER_TEMPLATE=fullstack-baseline # or: none (default)
The "boring baseline" template should include
- Auth — registration, login, logout, session/JWT
- RBAC — at least
admin / user roles
- Database — PostgreSQL or SQLite with a migration setup (e.g. Prisma, Alembic, or plain SQL)
- CRUD — one example resource end-to-end (e.g.
items or posts)
- Frontend stub — minimal UI wired to the API (optional, could be API-only first)
Stack options to evaluate
- Next.js + Prisma + PostgreSQL (most popular in vibe-coding circles)
- FastAPI + SQLAlchemy + PostgreSQL (Python-native)
- Rails (convention-over-configuration, batteries included)
- Reference: Flatlogic Web App Generator for inspiration on scope
UX flow
- User runs configurator → selects starter template
cloud-init.yaml includes STARTER_TEMPLATE=fullstack-baseline
- After provisioning, the workspace already has the repo cloned, deps installed, DB migrated, and dev server running
- User opens VS Code Web → starts vibing on features immediately, no setup
Acceptance Criteria
Notes
- Templates could live in a separate repo or as a subdirectory in this repo
- Long-term: multiple templates selectable from the configurator (baseline, SaaS, API-only, etc.)
- Inspired by community feedback from r/vibecoding 🙏
Feature Request
Problem
Right now RemoteVibeServer gets you from zero to a working dev environment very fast — but the first thing most users do is still bootstrap a new app from scratch. That means setting up auth, a database schema, RBAC, and basic CRUD before you can start vibing on the actual product.
Proposed Solution
Add an optional starter app template that gets deployed into the Coder workspace automatically, controlled by a config flag in the configurator.
Config flag (proposed)
In
cloud-init.yaml/ configurator:The "boring baseline" template should include
admin/userrolesitemsorposts)Stack options to evaluate
UX flow
cloud-init.yamlincludesSTARTER_TEMPLATE=fullstack-baselineAcceptance Criteria
STARTER_TEMPLATEadded to configurator and env filemain.tfor agent startup script)Notes