Skip to main content

Prerequisites

What a new engineer needs installed and access to before cloning the repo.

Tools​

  • .NET 10 SDK — backend (Logiswift.Eos.slnx).
  • Node.js (LTS matching frontend/src/eos-web/package.json's engines field if present, else current LTS) + npm — frontend (eos-web) and eos-contracts.
  • SQL Server client tooling — SSMS or Azure Data Studio — to inspect the sandbox database directly when debugging.
  • Git.
  • An IDE — Visual Studio 2022 or JetBrains Rider for the backend, VS Code for the frontend (any of the three work for either, this is just what the team mostly uses).

Access you'll need before you can run anything end-to-end​

  • VPN / network access to the sandbox database — Eos is database-first against a real SQL Server instance (ceva-eos is the shared dev sandbox); there's no seeded local database to fall back to. Ask your lead for VPN access if the connection times out.
  • The sandbox EosDb connection string — never committed (appsettings.*.json ships with an empty ConnectionStrings:EosDb). Get it from a teammate through a secure channel (password manager / Key Vault), not chat or email in plaintext. See Local Environment Setup for where it goes.
  • Repo access — this Git repo, plus the Azure DevOps project if you'll be touching pipelines.

Optional, needed for specific work​

  • Docker — only if you're adding/running Testcontainers-based integration tests (see backend/CLAUDE.md); not required for day-to-day feature work.
  • Azure CLI (az login) — only for the provisioning scripts under pipelines/scripts/ (Key Vault, App Insights, client onboarding). Most engineers won't touch these.

Next: Local Environment Setup.