Hmz.Template.Backend.ModularMonolith
0.4.0
See the version list below for details.
dotnet new install Hmz.Template.Backend.ModularMonolith@0.4.0
Hmz Modular Monolith Template
This folder is the canonical dotnet new template source for the Hmz .NET 10 backend.
Layout
modular-monolith/
├── Hmz.Template.Backend.ModularMonolith.csproj # NuGet template pack project
├── README.md # package README
└── content/ # generated project content
├── .template.config/template.json
├── Directory.Build.props
├── Directory.Packages.props
├── Hmz.Template.Backend.slnx
├── src/
├── tests/
└── docs/
The content folder is the source of truth for this template. Do not create another copy under templates/.
The generated solution currently consumes Hmz.Core.SharedKernel
0.1.18 and Hmz.Core.Testing 0.1.2; publish them to a configured NuGet
source before generating a project for normal use.
The current generated profile includes Logto JWT authentication, local UserManagement, and the optional application permission matrix. The matrix is not a requirement for every product generated from this template: API-key authentication, another identity provider, or an authentication-only API may remove the permission catalog, role-matrix endpoints, and permission authorization bundle together after generation.
The generated content is intentionally infrastructure-neutral. It ships only
the provider-neutral eng/ci/verify.sh gate and eng/ci/check-ignored-sources.sh;
it does not include release workflows, Coolify/VPS scripts, or a prescribed
migration runner. Add those to the generated application after implementation, based on
the selected hosting platform and operational requirements.
Pack
From the repository root:
dotnet pack .\modular-monolith\Hmz.Template.Backend.ModularMonolith.csproj `
--configuration Release `
--output .\artifacts\template-pack
The project file is the version authority and currently produces the
0.4.0 package. Do not override it while preparing the release, and never
republish an existing version. Publish Hmz.Core.SharedKernel 0.1.19,
Hmz.Core.Integrations 0.1.0 and Hmz.Core.Testing 0.1.3 first, verify
that a normal restore can resolve
them, then manually publish Hmz.Template.Backend.ModularMonolith.0.4.0.nupkg
using the maintainer's selected NuGet source and credentials.
Install and generate
$package = Get-ChildItem .\artifacts\template-pack\Hmz.Template.Backend.ModularMonolith.*.nupkg |
Sort-Object LastWriteTime -Descending |
Select-Object -First 1
dotnet new uninstall Hmz.Template.Backend.ModularMonolith
dotnet new install $package.FullName --force
dotnet new hmz-modular-monolith `
--name Acme.Ordering `
--output C:\Repos\Acme.Ordering `
--force
Run dotnet format <Name>.slnx once in the generated project. Renaming
Hmz.Template.Backend changes where the project's own namespaces sort among
the using directives, so eng/ci/verify.sh (dotnet format --verify-no-changes) reports import-ordering errors until it is formatted.
After generation, remove unused bundles from the generated project only. Never delete modules from this content source unless the template itself is intentionally changed.
This package has no dependencies.
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.