Description

This pull request introduces a new PowerShell script and accompanying documentation to streamline running multiple local FHIR R4 server instances behind an NGINX reverse proxy. The script automates environment setup, database initialization, project build/run, and proxy configuration, making it easier to launch, debug, and test a multi-instance cluster for development and E2E testing.

New multi-instance runner and documentation:

Multi-instance cluster orchestration

• Added start-local-fhir-nginx.ps1 script to automate launching multiple FHIR R4 server instances behind NGINX, including build, database setup, environment variable configuration, and log management.
• Script supports configurable parameters for instance count, ports, SQL connection, project path, framework, and logging, as well as optional flags for skipping build/schema initialization and persisting test environment variables.

NGINX proxy setup

• Script automatically downloads and configures NGINX if not present, generates a reverse proxy config to forward requests to backend FHIR instances, and manages proxy startup/shutdown.

Database and schema initialization

• Script normalizes SQL connection strings, ensures the target database exists (using sqlcmd), and applies the latest schema using the schema manager console.

Logging and debugging

• Supports per-instance log redirection, provides guidance for attaching Visual Studio debugger to running instances, and documents log locations for both FHIR and NGINX processes. [1] [2]

Comprehensive user documentation

• Added README.md detailing prerequisites, quick start, parameters, environment variables, stopping/cleanup, log locations, E2E test integration, sample endpoints, and debugging tips for the new multi-instance runner.

Related issues

Addresses AB#182969.

Testing

Tested locally while troubleshooting multi-pod caching issues in Search parameters

FHIR Team Checklist

• Update the title of the PR to be succinct and less than 65 characters
• Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
• Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
• Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
• Tag the PR with Schema Version backward compatible or Schema Version backward incompatible or Schema Version unchanged if this adds or updates Sql script which is/is not backward compatible with the code.
• When changing or adding behavior, if your code modifies the system design or changes design assumptions, please create and include an ADR.
• CI is green before merge
• Review squash-merge requirements

Semver Change (docs)

Patch|Skip|Feature|Breaking (reason)