Run Project Locally

There is no single root command for the full platform today. Start each repository separately.

Before starting, check the Local Runtime Matrix for default ports, env files, and infra dependencies.

Recommended startup order

Use this order unless your team tells you otherwise:

1. authentication service
2. setting service
3. data service
4. domain APIs such as ticket, GSB, NGOSS, NOC, TMF, or Vital as needed
5. portal frontend or mobile app
6. queue workers only if your flow depends on background processing

Backend services

Most backend services are NestJS apps and expose the same core commands.

Run in development mode:

pnpm run start:dev

Build for deployment:

pnpm run build
pnpm run start:prod

Frontend portal

The portal is an Angular application.

Current team flow appears to use the staging configuration so the frontend can talk to staging-backed APIs.

For most frontend work, developers only clone and run intt-portal, then rely on staging Swagger docs for API contracts.

Start portal with staging config:

pnpm run start:stg

or

ng serve --configuration=staging

Important note:

• pnpm run start and pnpm run serve currently point to the development Angular configuration
• if the team needs staging data, use pnpm run start:stg instead

Alternative commands already present in the repo:

pnpm run serve:stg
pnpm run serve
pnpm run start

Build:

pnpm run build

Mobile app

The mobile client is a Flutter application.

Install dependencies:

flutter pub get

Run locally:

flutter run

Target a specific device:

flutter devices
flutter run -d <device-id>

Environment selection uses --dart-define, for example:

flutter run -d <device-id> --dart-define=APP_ENV=STAG

Test commands

Portal:

pnpm run test

Backend services usually support:

pnpm run test
pnpm run test:e2e
pnpm run test:cov

Quick command reference

Project	Main local command
intt-mobile	flutter run
intt-portal	pnpm run start:stg
mvp1-authentication-service	pnpm run start:dev
mvp1-setting-service	pnpm run start:dev
mvp2-data-service	pnpm run start:dev
mvp3-caution-report-queue-service	pnpm run start:dev
mvp3-changedp-queue-service	pnpm run start:dev
mvp3-ctt-queue-service	pnpm run start:dev
mvp3-gsb-queue-service	pnpm run start:dev
mvp3-gsb-service	pnpm run start:dev
mvp3-kci-queue-service	pnpm run start:dev
mvp3-ngoss-service	pnpm run start:dev
mvp3-nocgrid-service	pnpm run start:dev
mvp3-nocpro-service	pnpm run start:dev
mvp3-ticket-service	pnpm run start:dev
mvp3-tmf-service	pnpm run start:dev
mvp6-tass-queue-service	pnpm run start:dev
mvp6-vital-queue-service	pnpm run start:dev
mvp6-vital-service	pnpm run start:dev

Validation checklist

After startup, verify:

• portal loads in browser
• mobile app launches on emulator or device when relevant
• login route works
• portal can reach staging-backed APIs when run with staging config
• backend services start without config or DB errors
• at least one business flow can load end-to-end
• queue workers can connect to broker or backing services when relevant

Gaps to document next

This page should later be expanded with:

• common local data seeding steps