Docker image for SCDMS and .NET Aspire integration (pgweb/pgAdmin-style)

[YBazanPro]

Hi,

I’m opening this issue to suggest a deployment and integration story that would greatly improve the experience for teams running SharpCoreDB in containerized and cloud-native environments.

Context: SCDMS as a web-based management studio

From the documentation, SCDMS (Sharp Core Database Management Studio) is now the recommended database studio for SharpCoreDB, replacing the legacy SharpCoreDB.Viewer Avalonia app. It is described as a local-first, cross-platform web UI that runs on your machine and opens in your browser, similar in spirit to pgweb or pgAdmin for PostgreSQL.[1][2][3]

Proposal

1. Official Docker image for SCDMS

• Publish an official Docker image for SCDMS (or a well-maintained Dockerfile template).
• The image would:
  • Run SCDMS as a lightweight web server.
  • Accept configuration via environment variables (e.g., default SharpCoreDB server URL, auth settings, TLS certs).
  • Expose a single HTTP/HTTPS port for browser access.

This would make it trivial to deploy SCDMS alongside SharpCoreDB server in any container environment.

2. .NET Aspire integration (pgweb/pgAdmin-style)

• Add first-class support for .NET Aspire, inspired by how PostgreSQL tooling is integrated:
  • A SharpCoreDB.Aspire package with something like:

    var builder = DistributedApplication.CreateBuilder(args);
    
    var sharpCoreDb = builder.AddSharpCoreDB("db")
     .WithServerContainer(); // SharpCoreDB server
    
    builder.AddSCDMS("admin")
     .WithReference(sharpCoreDb); // SCDMS container linked to DB

  • Aspire would then:
    • Spin up a SharpCoreDB server container.
    • Spin up an SCDMS container preconfigured to connect to that server.
    • Expose both as named resources with proper connection strings and URLs.
    • Integrate with the Aspire dashboard (health checks, logs, telemetry).

This pattern would be very similar to how pgweb/pgAdmin are used with PostgreSQL in Aspire: a dedicated admin UI container automatically wired to the database container.

3. Docker Compose samples

• Provide example docker-compose.yml files showing:
  • SharpCoreDB server + SCDMS.
  • Secure defaults (TLS, JWT/RBAC if applicable).
  • Volume mounts for data and configuration.

These samples could then be reused by the Aspire integration under the hood.

Benefits

• Much smoother onboarding for teams adopting SharpCoreDB in microservices or cloud-native architectures.
• A clear, “batteries-included” story for database administration in containerized environments.
• Strong alignment with the .NET Aspire ecosystem and modern deployment practices.

Is this something you would consider adding to the roadmap? If yes, I’d be happy to help with:

• Drafting Dockerfiles and Docker Compose samples for SCDMS + server.
• Experimenting with an Aspire extension package and sharing a prototype.

Thanks for your time and for the great work on SharpCoreDB and SCDMS.

[MPCoreDeveloper]

Implemented and published with v1.1.0 — all three parts are now live:

1. Official Docker image for SCDMS

• ghcr.io/mpcoredeveloper/scdms (1.1.0 + latest, linux/amd64 + linux/arm64).

2. .NET Aspire integration (pgweb/pgAdmin-style)

• SCDMS.Aspire.Hosting 1.1.0 on NuGet.org (AddSharpCoreDB + AddSCDMS + WithGrpcReference).
• Runnable AppHost example: examples/Aspire/SCDMS.AppHost.
• Pairs with the SharpCoreDB-side SharpCoreDB.Aspire.Hosting 2.0.0.2.

3. Docker Compose samples (three proxy options)

• Caddy (auto-TLS): samples/docker/
• YARP (all-.NET): samples/yarp/
• HAProxy (industry standard, incl. automatic Let's Encrypt ACME variant): samples/haproxy/

How to test - see docs/container-and-aspire-guide.md (run & test guide; section 5 = full end-to-end local recipe). Quick start:

cd samples/docker && cp .env.example .env && docker compose up -d # or:
dotnet run --project examples/Aspire/SCDMS.AppHost

Closing as implemented - thanks for the suggestion!