Environment Settings

Environment files define the routable environments, each environment's database connection and headers, and the hosts proxy endpoints may call.

File structure ​

/environments/
  ├── [EnvironmentName]/
  │   └── settings.json              # Environment settings
  ├── settings.json                  # Global settings
  └── network-access-policy.json     # Proxy target policy

Global settings ​

File: /environments/settings.json

{
  "Environment": {
    "ServerName": "SERVERNAME",
    "AllowedEnvironments": ["prod", "dev", "test"]
  }
}

Environment settings ​

File: /environments/[EnvironmentName]/settings.json

{
  "ServerName": "SERVERNAME",
  "ConnectionString": "Server=SERVERNAME;Database=prod;Trusted_Connection=True;Connection Timeout=15;TrustServerCertificate=true;",
  "Headers": {
    "DatabaseName": "prod",
    "ServerName": "SERVERNAME",
    "Origin": "Portway"
  }
}

Common headers: DatabaseName, ServerName, Origin; any header name is accepted.

Network access policy ​

File: /environments/network-access-policy.json

{
  "allowedHosts": [
    "localhost",
    "127.0.0.1"
  ],
  "blockedIpRanges": [
    "10.0.0.0/8",
    "172.16.0.0/12",
    "192.168.0.0/16",
    "169.254.0.0/16"
  ]
}

Connection strings ​

The provider is detected from ConnectionString. Per-provider examples, parameters, detection rules and capability differences: SQL providers.

SQLite paths are relative to the working directory. SQLite connection strings contain no credentials and are neither encrypted nor masked.

Secrets ​

Plaintext connection strings and authentication values are encrypted at the next start (PWENC:). Azure Key Vault is an alternative source (Environments, Azure Key Vault). Production SQL Server connections use Encrypt=true;TrustServerCertificate=false and credentials per environment.

Related topics ​

• Environments
• Entity Configuration
• Security
• Application Settings