appsettings.Development.json

{
  "//Serilog": "The EF Core command override is the only real change from appsettings.json. Locally the generated SQL is worth seeing; it stays at Warning everywhere else, because one line per query at Information is a volume problem in production and, with `Include Error Detail=true` in the connection string, a data-exposure one. Keep explanatory `//` keys OUT of MinimumLevel:Override — Serilog reads every key in that block as a logger name and every value as a level, so a comment there fails to parse as a LogEventLevel, is then treated as a LoggingLevelSwitch reference, and throws while the host is being built.",
  "Serilog": {
    "MinimumLevel": {
      "Default": "Information",
      "Override": {
        "Microsoft.AspNetCore": "Warning",
        "Microsoft.EntityFrameworkCore.Database.Command": "Information"
      }
    }
  },
  "SocialProviders": {
    "//": "Local-only OAuth fixtures for the endpoint workbench. SocialAuthService also checks that the host environment is Development, so this flag cannot enable demo identities in staging or production.",
    "DemoMode": true
  },
  "//ConnectionStrings": "NOT set here, on purpose — a connection string carries a password, and this file is committed. Development reads ConnectionStrings:Postgres from user-secrets (`dotnet user-secrets set \"ConnectionStrings:Postgres\" \"...\"`), other environments from the ConnectionStrings__Postgres environment variable (§25). Startup fails with a named error if neither is present. Add `Include Error Detail=true` to your local secret if you want Npgsql to put parameter values in exception messages — useful locally, a data leak anywhere else."
}