Update docs for Multitenancy.EFCore and configuration

Expanded documentation for CleanArchitecture.Extensions.Multitenancy.EFCore, including database-per-tenant setup and connection string resolution. Updated index, authentication, caching, and configuration reference docs to reflect new package, usage patterns, and recommended configuration sections. Added production release checklist to release notes.

Author: mheidari988

docs/extensions/multitenancy-efcore.md

@@ -147,12 +147,49 @@ builder.Services.AddCleanArchitectureMultitenancyEfCore(options =>
 });
 ```
 
+## Database-per-tenant setup
+
+```csharp
+builder.Services.AddCleanArchitectureMultitenancyEfCore(options =>
+{
+    options.Mode = TenantIsolationMode.DatabasePerTenant;
+    options.ConnectionStringFormat = "Server=.;Database=Tenant_{0};Trusted_Connection=True;TrustServerCertificate=True;";
+});
+
+builder.Services.AddDbContextFactory<ApplicationDbContext>((sp, options) =>
+{
+    options.UseSqlServer(builder.Configuration.GetConnectionString("DefaultConnection"));
+});
+
+builder.Services.AddTenantDbContextFactory<ApplicationDbContext>();
+```
+
+For request-scoped DbContext registration, resolve the tenant connection inside `AddDbContext`:
+
+```csharp
+builder.Services.AddDbContext<ApplicationDbContext>((sp, options) =>
+{
+    var currentTenant = sp.GetRequiredService<ICurrentTenant>();
+    var resolver = sp.GetRequiredService<ITenantConnectionResolver>();
+    var connectionString = resolver.ResolveConnectionString(currentTenant.TenantInfo);
+
+    if (string.IsNullOrWhiteSpace(connectionString))
+    {
+        throw new InvalidOperationException("Tenant connection string was not resolved.");
+    }
+
+    options.UseSqlServer(connectionString);
+});
+```
+
+`ITenantDbContextFactory<TContext>` sets the connection string per tenant for background tasks and migrations. Register your own resolver if connection strings live outside configuration.
+
 ## Key components
 
 - `TenantDbContext` base class, `ITenantDbContext`, and `TenantModelCacheKeyFactory`.
 - `TenantSaveChangesInterceptor` for tenant enforcement on writes.
 - `TenantModelCustomizer` for filters and schema configuration.
-- `TenantMigrationRunner<TContext>` for per-tenant migrations.
+- `TenantDbContextFactory<TContext>` + `TenantMigrationRunner<TContext>` for per-tenant connections and migrations.
 
 ## Related modules
 

docs/index.md

@@ -7,6 +7,7 @@ CleanArchitecture.Extensions is a small set of opt-in NuGet packages that plug i
 - `CleanArchitecture.Extensions.Caching`
 - `CleanArchitecture.Extensions.Multitenancy`
 - `CleanArchitecture.Extensions.Multitenancy.AspNetCore`
+- `CleanArchitecture.Extensions.Multitenancy.EFCore`
 
 ## Quickstart
 
@@ -42,12 +43,23 @@ dotnet add package CleanArchitecture.Extensions.Multitenancy.AspNetCore
 services.AddCleanArchitectureMultitenancyAspNetCore();
 ```
 
-No other template changes required.
+Multitenancy.EFCore:
+
+```powershell
+dotnet add package CleanArchitecture.Extensions.Multitenancy.EFCore
+```
+
+```csharp
+services.AddCleanArchitectureMultitenancyEfCore();
+```
+
+No template fork required.
 
 ## Where to go next
 
 - Caching docs: [extensions/caching.md](extensions/caching.md)
 - Multitenancy docs: [extensions/multitenancy-core.md](extensions/multitenancy-core.md)
 - Multitenancy.AspNetCore docs: [extensions/multitenancy-aspnetcore.md](extensions/multitenancy-aspnetcore.md)
+- Multitenancy.EFCore docs: [extensions/multitenancy-efcore.md](extensions/multitenancy-efcore.md)
 - Extensions catalog: [extensions/index.md](extensions/index.md)
 - Roadmap: [roadmap.md](roadmap.md)

docs/recipes/authentication.md

@@ -5,12 +5,12 @@ Wire authentication with extension-friendly hooks.
 
 ## Prereqs
 - Base Clean Architecture template running.
-- Auth provider chosen (e.g., JWT, IdentityServer) — placeholder until packages land.
+- Auth provider chosen (e.g., JWT, cookies, Identity) using the template defaults.
 
 ## Steps
-1. Add the relevant authentication adapter package (TBD).
-2. Configure authentication in Program.cs (or equivalent) with provided helpers.
-3. Add middleware/filters for tenant-aware auth if needed.
+1. Configure authentication in Program.cs (or equivalent) using the template guidance.
+2. If multitenancy is enabled, ensure tenant resolution runs before authorization checks.
+3. Add tenant-aware authorization policies if needed.
 
 ## Verify
 - Hitting a protected endpoint returns 200 with valid token; 401 otherwise.

docs/recipes/caching.md

@@ -5,7 +5,7 @@ Add caching with clear cache key conventions and opt-in behaviors.
 
 ## Prereqs
 - Base Clean Architecture template running.
-- Choose cache store (in-memory, distributed) — adapters TBD.
+- Choose cache store (in-memory default or an `IDistributedCache` implementation for distributed caching).
 
 ## Steps
 1. Add the caching package: `dotnet add package CleanArchitecture.Extensions.Caching`.

docs/reference/configuration.md

@@ -2,14 +2,55 @@
 
 Configuration keys and environment variables for extensions.
 
-- This section expands per extension as packages ship.
-- Include defaults, required values, and sample appsettings snippets.
+- Use the Options pattern to bind configuration sections to extension options.
+- Section names are not enforced; the names below are recommended for consistency.
 
 ## Available references
 
 - Multitenancy options: [multitenancy-options.md](multitenancy-options.md)
 
-## Placeholder keys
+## Recommended sections
 
-- Extensions:<Name>:Enabled
-- Extensions:<Name>:Options (TBD per extension)
+- `Extensions:Caching` -> `CachingOptions`
+- `Extensions:Caching:QueryBehavior` -> `QueryCachingBehaviorOptions`
+- `Extensions:Multitenancy` -> `MultitenancyOptions`
+- `Extensions:Multitenancy:AspNetCore` -> `AspNetCoreMultitenancyOptions`
+- `Extensions:Multitenancy:EFCore` -> `EfCoreMultitenancyOptions`
+
+## Example
+
+```json
+{
+  "Extensions": {
+    "Caching": {
+      "Enabled": true,
+      "DefaultNamespace": "MyApp",
+      "QueryBehavior": {
+        "DefaultTtl": "00:05:00",
+        "CacheNullValues": false
+      }
+    },
+    "Multitenancy": {
+      "RequireTenantByDefault": true,
+      "HeaderNames": [ "X-Tenant-ID" ],
+      "EFCore": {
+        "Mode": "SharedDatabase",
+        "TenantIdPropertyName": "TenantId"
+      }
+    }
+  }
+}
+```
+
+Bind sections in your host:
+
+```csharp
+builder.Services.Configure<CachingOptions>(
+    builder.Configuration.GetSection("Extensions:Caching"));
+builder.Services.Configure<QueryCachingBehaviorOptions>(
+    builder.Configuration.GetSection("Extensions:Caching:QueryBehavior"));
+builder.Services.Configure<MultitenancyOptions>(
+    builder.Configuration.GetSection("Extensions:Multitenancy"));
+builder.Services.Configure<EfCoreMultitenancyOptions>(
+    builder.Configuration.GetSection("Extensions:Multitenancy:EFCore"));
+```

docs/release-notes/index.md

@@ -2,5 +2,15 @@
 
 Changelog for CleanArchitecture.Extensions (latest-only for now).
 
-- Add a section per release once packages ship.
-- Call out breaking changes and migration steps.
+## Unreleased
+
+- No public releases yet.
+
+## Production release checklist
+
+- Package metadata validated (`README`, license, icon, SourceLink, symbols).
+- Docs updated for all shipped packages (install, config, quickstart).
+- CI green: unit tests + basic integration tests for EFCore behaviors.
+- Sample integration against the template works without forked changes.
+- Breaking changes documented with migrations (if any).
+- Security/behavior caveats documented (caching, tenant enforcement, isolation).

src/CleanArchitecture.Extensions.Multitenancy.EFCore/README.md

@@ -144,6 +144,43 @@ builder.Services.AddCleanArchitectureMultitenancyEfCore(options =>
 });
 ```
 
+## Database-per-tenant setup
+
+```csharp
+builder.Services.AddCleanArchitectureMultitenancyEfCore(options =>
+{
+    options.Mode = TenantIsolationMode.DatabasePerTenant;
+    options.ConnectionStringFormat = "Server=.;Database=Tenant_{0};Trusted_Connection=True;TrustServerCertificate=True;";
+});
+
+builder.Services.AddDbContextFactory<ApplicationDbContext>((sp, options) =>
+{
+    options.UseSqlServer(builder.Configuration.GetConnectionString("DefaultConnection"));
+});
+
+builder.Services.AddTenantDbContextFactory<ApplicationDbContext>();
+```
+
+For request-scoped DbContext registration, resolve the tenant connection inside `AddDbContext`:
+
+```csharp
+builder.Services.AddDbContext<ApplicationDbContext>((sp, options) =>
+{
+    var currentTenant = sp.GetRequiredService<ICurrentTenant>();
+    var resolver = sp.GetRequiredService<ITenantConnectionResolver>();
+    var connectionString = resolver.ResolveConnectionString(currentTenant.TenantInfo);
+
+    if (string.IsNullOrWhiteSpace(connectionString))
+    {
+        throw new InvalidOperationException("Tenant connection string was not resolved.");
+    }
+
+    options.UseSqlServer(connectionString);
+});
+```
+
+`ITenantDbContextFactory<TContext>` switches the connection string per tenant for background tasks and migrations. Register a custom resolver if you want to pull connection strings from a vault or catalog.
+
 ## What to expect
 
 - Shared database mode automatically adds a tenant filter (`TenantId`) to all tenant-scoped entities.