🚀 Getting Started

• .NET 10.0 SDK - Download from Microsoft
• Docker Desktop - For the database (MongoDB / PostgreSQL / SQL Server), Redis, Kafka, and containerized deployment
• IDE: Visual Studio 2022, VS Code, or JetBrains Rider
• Git - For version control

1. Clone the repository:
   git clone https://github.com/BlazorBlueprint/Blazor-Blueprint.git your-saas-app
cd your-saas-app
2. Restore dependencies:
   dotnet restore BlazorBlueprint.sln
3. Build the solution:
   dotnet build BlazorBlueprint.sln

Option 1: .NET Aspire (Recommended)

1. Provide the database: For the default MongoDB backend, run local MongoDB or configure a cloud connection in appsettings.json. For postgresql / sqlserver, the Aspire AppHost provisions the container automatically — no separate step.
2. Set Dev/BlazorBlueprint.AppHost as startup project in Visual Studio
3. Press F5 or click Run
4. Aspire dashboard opens automatically showing all services
5. Click the Web endpoint to access your application

Option 2: Manual Setup

If you prefer not to use Aspire:

1. Start the database and Redis: (default MongoDB backend shown)
   docker run -d --name mongodb -p 27017:27017 mongo:latest
docker run -d --name redis -p 6379:6379 redis:latest
2. Update connection strings in appsettings.json:
   "Database": { "DatabaseType": "mongodb", "ConnectionString": "mongodb://localhost:27017" }
"ConnectionStrings": { "redisCache": "localhost:6379" }

   Set DatabaseType to postgresql or sqlserver (with a matching ConnectionString) to run on a relational backend instead.

3. Run the web application:
   dotnet run --project Web/BlazorBlueprint.Web

1. Access the application: Navigate to the Web endpoint shown in the Aspire dashboard (port changes each run)
2. Complete initial setup: A fresh install auto-redirects to /initial-setup, where you create the first Owner account and the platform organisation. (The Register page is for later members — it creates a regular member, not an admin.)
3. Land on the app launcher: After signing in (and any org selection / creation), you'll land on /apps — an Odoo-style tile grid of installed plugins plus an Admin tile for organisation settings and a Platform Admin tile for platform-level management. The launcher is the canonical home for signed-in members and is controlled by Features:AppLauncher (default on).
4. Build and explore plugins: The template ships with no bundled plugins — you build your own against the IPlugin model. Each installed plugin opens from the launcher into its own dashboard under a plugin-specific sidebar (/plugin/{your-plugin}/...), with settings under /admin/plugin/{your-plugin}/....
5. View infrastructure: Visit Infrastructure Monitor to see system status (requires a platform admin account)