Developer

Overview of the Wakapp architecture: multi-tenant hierarchy, services, communication flows and access modes.

Using the Discovery service to resolve a user's organization before authentication.

Overview of the Wakastart OAuth2 PKCE flow: key concepts, complete diagram and Keycloak prerequisites.

Complete PKCE flow code: generation, start-login, exchange, enrichment, cookies and logout.

Complete structure of the /me payload: identity, access levels, teams, application rights and features.

When to call /me, React caching strategy, invalidation after token refresh and best practices.

Wakastart's 2 rights vectors: adminLevel and appRights (resource.action rights), and enabled-feature checks.

Full implementation: useAppRights hook, Protected component, NestJS AppRightGuard.

App/Network/Customer feature cascade, conditional activation and integration in guards.

Tokens, secrets, HTTPS, CSP, logs: the non-negotiable security rules for a Wakapp in production.

Cache, proactive refresh, pagination, TanStack Query, Prometheus metrics, and structured logging.

The 10 most frequent mistakes when integrating a Wakapp: symptom, cause and solution.

Authenticating requests, pagination, filters, automatic multi-tenancy, and unified error format.

Required and optional headers, idempotency, CORS, rate limiting and exponential backoff.

Exhaustive table of all Discovery, Auth, profile, CRUD, invitations and modules endpoints available for a WakaApp.

Unified error format, HTTP codes 400 to 5xx, causes and handling strategies for a robust Wakapp.

Wakastart business error codes, exact messages that can be tested programmatically, and status mappings.

Create an invitation: prerequisites, POST /api/invitations endpoint, body, response and error handling.

The verify and accept endpoints: implementing the acceptance page, server-side effects and pitfalls.

The WakaStart MCP server hosted on docs.wakastart.app: 5 tools, available resources and technical characteristics.

Configure Claude Code with .mcp.json to access the WakaStart MCP server at docs.wakastart.app.

Wakastart is a PaaS platform that hosts your app — you declare its components, Wakastart builds and runs them.

Wakastart's hierarchical model: Architecture (the blueprint) vs Environments (the actual instances).

Describe your wakapp's infrastructure in a JSON file and import it in a few clicks — get started fast, clone an app, or let an AI generate the skeleton.

Managed or imported repos: the source of the code you'll build.

ServiceDefinition (architecture) vs ServiceInstance (environment): the 2-level pattern.

The pipeline that turns your Git code into a deployable Docker image.

PostgreSQL, MongoDB, Valkey, and S3 buckets: your app's persistent dependencies.

Domains, subdomains, and HttpRoutes: how Wakastart routes HTTP traffic to your services.

How Wakastart delivers config to your services: architecture, environment configuration, binding.

Redirect a Network or Customer subdomain to an existing application route, via a shared HAProxy component.

An environment = a complete, isolated instance of your app. Main fields, lifecycle, dashboard.

Statuses PENDING → PROVISIONING → PROVISIONED → DESTROYING → DESTROYED.

Crucial difference: a Build produces an image, a Deployment launches pods. AUTO vs MANUAL mode.

End-to-end walkthrough: create the App, define the architecture, trigger a build, deploy to dev then to prod.

Concrete rules for an application service to run correctly on Wakastart: .env.example, Dockerfile, Prisma migrations, data seeding, runtime config, S3, OAuth.

Technical vocabulary of hosting: PaaS, K8s, Pod, Docker image, S3 Bucket, Gateway, etc.

Interactive OpenAPI spec of the WakaStart Public API — browse endpoints, try requests.

Visual documentation of @wakastellar/ui components — interactive examples, props, and variants.