Replace nginx with aspnet core hosting

[damianh]

Summary

Replace the nginx-based static file serving with an ASP.NET Core application and restructure the repository to separate Astro content from the .NET server.

What changed

Architecture: nginx → ASP.NET Core (server/src/Docs.Web)

• ASP.NET Core app serves Astro's static output with production-grade caching, response compression, trailing-slash redirects, and custom 404 handling — replicating the existing nginx behavior.
• Redirect middleware loads redirects.json (generated by Astro build from redirect_from frontmatter) and performs 301 redirects with case-insensitive matching.
• Dockerfile-free container publishing via dotnet publish /t:PublishContainer targeting aspnet:10.0-alpine.
• Removed Dockerfile, .dockerignore, and deployment/ (nginx configs).

Repository restructure

• Moved all Astro source files into an astro/ subdirectory to cleanly separate content from the .NET server.
• Server projects organized into server/src/ and server/tests/ subdirectories.
• Astro builds in a Docker container (node:22-slim) to avoid cross-platform npm issues with native modules like sharp and resvg-js.

Build orchestration (build.cs)

• Single entry point with targets: astro-build, dotnet-build, dotnet-test, container, aspire, link-check, verify-formatting, clean.
• CI workflows updated to use dotnet build.cs <target>.

Integration tests (server/tests/Docs.Web.Tests)

• Tests for redirect middleware covering exact match, case-insensitive match, trailing-slash normalization, passthrough for unknown paths, and JSON-body passthrough.
• Uses WebApplicationFactory with isolated temp wwwroot and test redirects.json.

Local development with .NET Aspire (server/src/Docs.AppHost)

• dotnet build.cs aspire orchestrates the Astro dev server (port 4321) and the ASP.NET Core app together with OpenTelemetry, health checks, and the Aspire dashboard.

New project structure

├── astro/                          # Astro site (content, components, config)
│   ├── src/content/docs/           # All documentation markdown
│   ├── src/plugins/                # Astro plugins (static-redirects.ts)
│   ├── package.json
│   └── astro.config.mjs
├── server/                         # .NET 10 solution
│   ├── src/
│   │   ├── Docs.Web/               # ASP.NET Core static file server
│   │   ├── Docs.AppHost/           # .NET Aspire orchestrator
│   │   └── Docs.ServiceDefaults/   # Shared OpenTelemetry & health checks
│   ├── tests/
│   │   └── Docs.Web.Tests/         # Integration tests
│   └── Docs.slnx
├── build.cs                        # Build script
└── README.md

Build & run

# Full container build (Astro + .NET publish → OCI image)
dotnet build.cs container

# Local development with Aspire
dotnet build.cs aspire

# Just build Astro
dotnet build.cs astro-build

# Run tests
dotnet build.cs dotnet-test

Files removed

• Dockerfile, .dockerignore
• deployment/default.conf, deployment/nginx.conf
• build.sh

[maartenba]

The nginx redirects being added by static-redirects.ts don't seem to be considered by the ASP.NET Host, can you look into this @damianh ?

[damianh]

Good catch — fixed. The static-redirects.ts plugin now outputs a redirects.json map instead of the nginx redirect.conf. On the ASP.NET Core side, a redirect middleware in Program.cs loads that JSON at startup and performs 301 redirects with case-insensitive matching. Trailing slashes are normalized before lookup. Also added some tests.

[maartenba]

Use writing guidelines/styles

[duende-github-bot]

Preview Environment Provisioned

[maartenba]

I'm good with it. @damianh let's merge Monday EU AM