Skip to main content

Onboarding Overview

This section helps a new team member go from zero context to a working local setup.

Goals​

By the end of onboarding, a developer should be able to:

  • understand the main Antrix repositories
  • install the required tools
  • clone and install dependencies for each service
  • start the frontend and relevant backend services
  • know where to look for architecture and troubleshooting notes

Repository layout​

The current workspace is organized as multiple sibling folders:

INTT/
  intt-docs/
  intt-mobile/
  intt-portal/
  mvp1-authentication-service/
  mvp1-setting-service/
  mvp2-data-service/
  mvp3-caution-report-queue-service/
  mvp3-changedp-queue-service/
  mvp3-ctt-queue-service/
  mvp3-gsb-queue-service/
  mvp3-gsb-service/
  mvp3-kci-queue-service/
  mvp3-ngoss-service/
  mvp3-nocgrid-service/
  mvp3-nocpro-service/
  mvp3-ticket-service/
  mvp3-tmf-service/
  mvp6-tass-queue-service/
  mvp6-vital-queue-service/
  mvp6-vital-service/

This means:

  • there is no single root command that starts everything
  • each service has its own install, run, and test commands
  • central documentation is easier to maintain from intt-docs
  • some repositories are background workers and may not need to run for every developer task
  • Antrix now has both web and mobile client surfaces

Suggested onboarding order​

  1. Read the System Overview
  2. Set up local tooling from Prerequisites
  3. Prepare repositories using Local Setup
  4. Check ports, env files, and dependencies in Local Runtime Matrix
  5. Start services from Run Project Locally
  6. Read the relevant pages under Services

Choose your track​

What to ask the team early​

Some setup details are usually environment-specific and should be confirmed early:

  • required .env or config files for each service
  • database access for local development
  • SSO or OIDC credentials for intt-portal
  • whether Docker is used for shared local dependencies
  • which services are mandatory for your workstream

For a new joiner, a good first milestone is:

  1. start mvp1-authentication-service
  2. start mvp1-setting-service
  3. start mvp2-data-service
  4. start mvp3-ticket-service or mvp3-gsb-service if relevant
  5. start intt-portal
  6. verify login and one basic page flow

Queue services can be added later when your work touches async processing or integration flows.

If your workstream is mobile, replace portal setup with intt-mobile and verify one end-to-end app flow on a device or emulator.