Getting Started

Kinoder consists of a Nuxt frontend, NestJS API, separate worker, PostgreSQL, Redis, private object storage, and Caddy gateway. The complete-stack workflow uses Docker Compose from the backend repository.

Before installation

Prepare Docker with Compose, sibling frontend and backend checkouts, persistent database and storage volumes, a public HTTPS domain for production, deployment-owned secrets, and production SMTP. Stripe, AI providers, Google Fonts, managed storage, and social providers are optional until enabled.

Recommended order

1. Review Configuration.
2. Configure secrets and infrastructure.
3. Build API, worker, and frontend images.
4. Apply database migrations.
5. Verify liveness, readiness, HTTPS, and worker connectivity.
6. Create and verify the first account.
7. Promote an administrator only when bootstrap or recovery requires it.
8. Configure storage, billing, provider routes, pricing, and alerts.

IMAGE PLACEHOLDER - Healthy installation Replace with screenshots of healthy Compose services and the Kinoder sign-in screen over HTTPS. Recommended combined canvas: 1800 x 1000 px. Redact private hosts and addresses.

Pulling source does not update running containers. Rebuild affected images, apply migrations, and verify the served application after every update.