Skip to main content
Fleet Manager is a Python 3.12 codebase built around a typed API layer, a Temporal-based workflow engine, background agents, and supporting CLIs for deployment and operations.

​
Developer Onboarding

Before working in the codebase, you’ll typically need:
  • Repository access to nscaledev/fleet-manager
  • 1Password access to the Fleet Manager vaults (see Getting Access)
  • Teleport access to the management environment for any work against shared dev infrastructure
Raise access requests in the #fleet-manager-chat Slack channel.

​
Local Setup

Clone the repository and set up the local environment from the repo root:
After setup, the CLI is available as:

​
Teleport and Management Network

Most development work assumes access to the management network. For the shared dev environment, engineers typically work from management VMs such as app51. Authenticate with Teleport first:
Then connect to the target VM with the login shown in the Teleport profile output:
If you need regular SSH access to Teleport hosts, configure it:

​
Runtime Configuration

Fleet Manager expects explicit environment configuration:
  • ENVIRONMENT selects the runtime environment (local, dev, stg, uat, prod)
  • OP_VAULT_SELECTOR selects the target Fleet Manager vault (for example hub, sta1, glo1)
  • API_DEBUG defaults to false; set API_DEBUG=true only for local Django debug pages
Local development runtimes still map to the dev vault for credentials while keeping separate local runtime behaviour.

​
How To Read The Developer Docs

​
Important Agent Skills

Shared agent skills live under .agents/skills/. Ask the coding agent to use a skill by name when you want its workflow applied explicitly; mandatory skills also activate from the files and systems being changed.

​
Contributing to the Docs

The published docs are sourced from this repository. If you find drift, gaps, or stale instructions:
  • Open a pull request against nscaledev/fleet-manager
  • Update the relevant source doc under docs/ or docs/published/
  • Keep deployment runbooks and published pages aligned when behaviour changes

​
Current Focus

The published developer guide currently emphasises:
  • Overall architecture and dependency boundaries
  • Hub/satellite deployment architecture
  • Workflow authoring
API integration, agent authoring, and hardware-test authoring pages exist as placeholders and will be populated as the source material is split out of the repo’s internal docs.