26 lines
1.6 KiB
Markdown
26 lines
1.6 KiB
Markdown
# Developer quick guide
|
|
|
|
**Current phase:** Foundation only. No `npm install`, Docker build or login preview is available yet.
|
|
|
|
## Where to make changes (after later phases)
|
|
- Login / signup / password recovery appearance: `auth/ui/v2/`.
|
|
- Account dashboard appearance: `users/ui/`.
|
|
- Reusable color tokens and components: `packages/` (only after created).
|
|
- ZITADEL image/config, not Go application code: `core/backend/zitadel/`.
|
|
- Compose, HTTPS routing and service configuration: `deployment/`.
|
|
|
|
## Planned local development
|
|
1. Install Git, Node.js with compatible pnpm and Docker Desktop.
|
|
2. Start a **local-only** ZITADEL + PostgreSQL stack using a later phase's documented script.
|
|
3. Start Login V2 and Account UI in Next.js development mode (hot reload).
|
|
4. Use test accounts, synthetic profile data and local-only UI states.
|
|
5. Inspect mobile/desktop, keyboard accessibility and full auth flows before any production build.
|
|
|
|
Commands, required versions and ports will be documented when the real upstream dependencies are installed. Do not guess them from this scaffold.
|
|
|
|
## Working with AI Studio / coding agents
|
|
Ask for changes scoped to JSX/TSX, CSS and design tokens. Review the resulting diff before integrating. Never paste generated mock auth, fake JWT handlers or browser-side admin API credentials into production. Protected auth/route code requires separate approval and focused security testing.
|
|
|
|
## Deployment rule
|
|
Coolify must use an explicit, production-safe Compose configuration. Local overrides and secrets must not be copied into production. Production deploy is not part of Phase 01.
|