Run Kinora locally

Open every terminal where the commands below expect it: inside kinora-fitness-full-stack for the full stack, or next to the app's folder for a single-app package.

Start the API first: with the steps below the dashboard reads all of its data from it.

Start the API

1. 01

   Install and configure

   .env.example works as it is for local development.

   TerminalCopy

   corepack enable
   cd back-end
   yarn install
   cp .env.example .env

   Watch step0:09

   Having trouble?

   I've done this step
2. 02

   Create the database

   yarn seed creates database.sqlite, its tables and the demo data. Running it again adds only what is missing.

   Terminalin back-endCopy

   yarn seed

   I've done this step
3. 03

   Start the server

   Terminalin back-endCopy

   yarn dev

   Expected result: localhost:8000/api/healthLocal answers {"status":"ok"}.

   Having trouble?

   I've done this step

Start the API

1. 01

   Install and configure

   .env.example works as it is for local development.

   TerminalCopy

   corepack enable
   cd kinora-fitness-backend
   yarn install
   cp .env.example .env

   Watch step0:09

   Having trouble?

   I've done this step
2. 02

   Create the database

   yarn seed creates database.sqlite, its tables and the demo data. Running it again adds only what is missing.

   Terminalin kinora-fitness-backendCopy

   yarn seed

   I've done this step
3. 03

   Start the server

   Terminalin kinora-fitness-backendCopy

   yarn dev

   Expected result: localhost:8000/api/healthLocal answers {"status":"ok"}. The seed printed the accounts to sign in with.

   Having trouble?

   I've done this step

Start the dashboard

In a second terminal:

1. 01

   Install and configure

   TerminalCopy

   cd dashboard
   yarn install
   cp .env.example .env

   Watch step0:09

   I've done this step
2. 02

   Point it at the API

   Open dashboard/.env and fill in the two API lines, which are empty in the example. Left empty, the dashboard runs on its built-in sample data instead of the API.

   dashboard/.envCopy

   NEXT_PUBLIC_API_BASE_URL=http://localhost:8000/api
   NEXT_PUBLIC_WEBSOCKET_BASE_URL=http://localhost:8000

   I've done this step
3. 03

   Start it and sign in

   Terminalin dashboardCopy

   yarn dev

   Expected result: localhost:3030Local opens the sign-in form, filled in with the Head Coach: headcoach@example.com with the password Coach@123. /en/auth/login?as=client fills in the member, member@example.com with Member@123. Arabic is at /ar.

   Having trouble?

   I've done this step

Start the dashboard

The API is not part of this package. Do not create a .env file yet: without one, the dashboard runs on its built-in sample data.

1. 01

   Install

   TerminalCopy

   corepack enable
   cd kinora-fitness-dashboard
   yarn install

   Watch step0:09

   Having trouble?

   I've done this step
2. 02

   Start it and sign in

   Terminalin kinora-fitness-dashboardCopy

   yarn dev

   Expected result: localhost:3030Local opens the sign-in form with a "Sample data" notice. The password is not checked (the form still asks for at least 6 characters), and what you change is kept in the browser.

   I've done this step

Production build

The same folders, built once and then started. First set back-end/.env for production. With NODE_ENV=production the API never rewrites the schema on its own: it runs the migrations as it starts. It refuses to start while JWT_SECRET is empty or still the example value, or while CORS_ORIGIN is empty.

NODE_ENV=production
JWT_SECRET=<a long random string>
CORS_ORIGIN=http://localhost:3030
FRONTEND_URL=http://localhost:3030

Generate the secret with node -e "console.log(require('crypto').randomBytes(48).toString('hex'))". Then build the API, create its tables once, and start it. yarn db:sync:prod creates empty tables; yarn seed:prod in its place, or after it, adds the demo data and its accounts.

yarn build
yarn db:sync:prod
yarn start:prod

Then the dashboard, on 3030:

yarn build
yarn start

The dashboard compiles its .env in at build time, so run yarn build again after changing it. Before you deploy anywhere public, read the production checklist.

• Going live

Production build

Built once, then started. First set .env for production. With NODE_ENV=production the API never rewrites the schema on its own: it runs the migrations as it starts. It refuses to start while JWT_SECRET is empty or still the example value, or while CORS_ORIGIN is empty.

NODE_ENV=production
JWT_SECRET=<a long random string>
CORS_ORIGIN=https://app.your-domain.com

Generate the secret with node -e "console.log(require('crypto').randomBytes(48).toString('hex'))". CORS_ORIGIN lists the addresses of the dashboards that call the API, comma separated. Then build, create the tables once, and start. yarn db:sync:prod creates empty tables; yarn seed:prod in its place, or after it, adds the demo data and its accounts.

yarn build
yarn db:sync:prod
yarn start:prod

• Going live

Production build

Built once, then started on 3030. With no .env the production build runs on the sample data exactly as yarn dev does.

yarn build
yarn start

The dashboard compiles its .env in at build time, so run yarn build again after changing it.

Start over with fresh demo data

Stop the API, then delete the database file and seed it again, in the API's folder. This deletes everything you created.

rm -f database.sqlite* && yarn seed

In PowerShell:

Remove-Item database.sqlite*; yarn seed

Next

• Set your environment variables
• Run it with Docker instead
• Fix a setup problem