Foundry CLI 0.2.3 – Tooling, API consistency & single-tenancy polish Latest

Boilerplate single-tenancy (React + API) + CLI

This release tightens the Foundry CLI and the single-tenancy stack: generated projects get the same name substitution in shell/Batch migration helpers and Docker Compose (.sh, .bat, .yml), not only in .cs / .json. The CLI README now matches the real flow—templates downloaded from GitHub Releases and cached under %LocalAppData%—and calls out how single-tenancy (open signup + email code verification) differs from multi-tenancy (invites / tenants).

Note: Executors and templates.zip stay out of the repo and are published as release assets so clones stay small; the CLI pulls the right package when it runs.

Highlights

• Single-tenancy auth: remove the link-only confirm path; register → code by email → VerifyEmail / resend is the supported flow.
• API: user-facing BoilerplateResponse / auth-related messages standardized to English (single + multi templates).
• Backend hygiene: Boilerplate.Application.Dtos namespace alignment; removed stray NewLevel.* DTO namespaces and the duplicate EmailDto in the multi-tenant Application project.
• CLI: safer rename pass (only rewrite files that still contain Boilerplate), removed unused temp cleanup, “Preparing templates…” messaging, and script + Compose files included in the replace step.
• React (single): locale files trimmed to keys the app uses; notifications.* aligned with CreateNotificationModal / NotificationCenter; apiClient import / dead refresh-helper cleanup.

CLI: generated project files

After scaffolding, these now participate in Boilerplate → project name replacement (when they contain the placeholder):

• apply-migrations-*.bat / apply-migrations-*.sh
• create-migrations-*.bat / create-migrations-*.sh
• docker-compose.yml (e.g. container names / references)

For operators

• Ensure the release tag referenced by the CLI matches the templates.zip (and optional executors) you publish for 0.2.2.
• First run may require network access to download templates; later runs reuse the LocalAppData cache until the version folder changes or is deleted.

Upgrade notes (existing apps from older templates)

• Single-tenancy: if you still expose GET confirm-email, clients or emails pointing to that URL should move to the code + POST VerifyEmail flow (or keep a custom link flow in your fork).
• API clients that assumed Portuguese error strings may need to adjust expectations; messages are now English for consistency.

---

For day-to-day use, install or run the Foundry CLI to scaffold a project as usual; rely on GitHub Releases for packaged templates and executors instead of copying them from the repository.

Foundry CLI 0.2.3 – Single-tenancy auth & release artifacts · Latest

Boilerplate single-tenancy (React + API)

This release updates the single-tenancy boilerplate around sign-in and onboarding: the login experience now supports email delivery and verification with a code, so users can confirm their address as part of the flow. Self-service registration is supported end to end—you no longer need invites; signing up is enough to get started.

Note: Executors and the templates.zip package are no longer stored in the repository. They had grown large and were making the CLI heavy to clone and ship. From this version onward, those assets are attached only to GitHub Releases; the CLI downloads templates at runtime when needed (nothing is embedded in the executable). A local templates.zip is still produced on dotnet build of Foundry.CLI so you can upload it to the matching release tag.

• Single-tenancy auth: Email sending and code-based verification in the login/register flow; link-only confirm-email removed from the template.
• Register without invites—open registration instead of invite-only onboarding for the single-tenant app.
• Lighter repo: executors and templates.zip live as release attachments; the CLI fetches from releases instead of bundling everything in the tree.
• API: user-facing messages in English where it matters (auth, forgot/reset password, etc.) in both single and multi templates for consistency.
• Backend hygiene: Boilerplate.Application.Dtos namespaces aligned; stray NewLevel.* DTO namespaces removed in multi; duplicate EmailDto under Auth removed.
• CLI UX: after download/prepare you see “Templates ready.” and prompts continue without a misleading “press any key” pause; successful runs exit immediately; on errors, an optional key wait runs only when the console is interactive (not when stdin is redirected).
• CLI rename pass: Boilerplate → project name also applies to .bat, .sh, .yml / .yaml (migration helpers and docker-compose), not only .cs / .json; files without the placeholder are skipped.
• React (single): locale JSON trimmed to keys the app uses; notifications.* aligned with CreateNotificationModal / NotificationCenter; apiClient import and dead helper cleanup.

Multi-tenancy is unchanged as a product: invites, tenant, and confirm-email by link remain where they already existed; it benefits from the same English API messages and Dtos cleanup.

Operators: publish templates.zip on the GitHub Release whose tag matches the version string in Program.cs. Users with an existing cache under %LocalAppData%\BoilerplateCustomizer\<version>\extracted only re-download if they delete that folder or you ship a new templates release tag.

Upgrading an old generated single-tenant app: prefer scaffolding a new project with the current CLI, or manually adopt the code-only email verification flow (no link confirm endpoint), English API strings, and the React locale / apiClient updates if you copied the boilerplate frontend.

For day-to-day use, install or run the Foundry CLI and scaffold a project as usual; rely on GitHub Releases for packaged templates and executors rather than copying files from the repository.

Foundry CLI 0.2.2 – Single-tenancy auth & release artifacts

🚀 Boilerplate single-tenancy (React + API)

This release updates the single-tenancy boilerplate around sign-in and onboarding: the login experience now supports email delivery and verification with a code, so users can confirm their address as part of the flow. Self-service registration is supported end to end—you no longer need invites; signing up is enough to get started.

⚠️ Note: Executors and the zipped templates package are no longer stored in the repository. They had grown large and were making the CLI heavy to clone and ship. From this version onward, those assets are attached only to GitHub Releases; the CLI downloads templates (and related artifacts) directly from releases when needed.

Email sending and code-based email verification in the single-tenancy login/register flow
Register without invites—open registration instead of invite-only onboarding
Lighter repo: executors and templates.zip moved to release attachments; CLI fetches from releases instead of bundling everything in the tree
For day-to-day use, install or run the Foundry CLI and scaffold a project as usual; rely on releases for packaged templates and executors rather than copying files from the repo.

Foundry CLI 0.2.1 – Template

🚀 Boilerplate CLI Templates

This package contains the templates used internally by the Boilerplate CLI to generate new projects.

⚠️ Note: This file is not intended for direct use. It is automatically downloaded and processed by the CLI.

• Provides base project structure and configuration
• Used during project scaffolding
• Versioned to support updates and improvements

For proper usage, run the CLI instead of using this file manually.

Foundry CLI 0.2.1 – Standardized Response & Error Handling

🚀 Release v0.2.1

This release introduces a major improvement in how responses and errors are handled across the application, improving consistency, maintainability, and architectural separation.

✔ Introduced a standardized Result pattern in the application layer for handling success and failure scenarios
✔ Replaced exception-driven business logic with explicit result-based flow control
✔ Implemented structured error handling using Error and ErrorType for better semantic clarity
✔ Decoupled application logic from HTTP concerns (no direct status handling outside controllers)
✔ Simplified controllers by centralizing error-to-HTTP mapping (MapError)
✔ Refactored validation flow to return consistent and predictable responses
✔ Improved overall code readability and testability

⚠️ Note:
Business rule errors are no longer handled via exceptions. Instead, they are returned through the Result pattern. Exceptions are now reserved for unexpected or infrastructure-related failures and are handled by middleware.

This is still a pre-release version. While the new response pattern is stable, further refinements and standardizations (such as response extensions and validation pipelines) may be introduced in future iterations.

Foundry CLI 0.2.0 – Redis Support Added

This release of Foundry CLI introduces optional Redis support for caching and rate-limiting, giving developers more flexibility and performance improvements for larger projects.

✔ Optional Redis integration for caching and rate-limiting
✔ In-memory fallback if Redis is not enabled
✔ Fixed all compiler warnings for cleaner builds
✔ Updated README to include instructions for chmod on Linux/macOS, ensuring executables can be run without permission issues
✔ Cross-platform support maintained (Windows, Linux, macOS)
✔ Self-contained binaries for easy setup
✔ Project scaffolding automation

⚠️ Note: If Redis is not enabled, Foundry CLI will use in-memory caching via C#. While functional, this may not scale for multi-instance or heavy-load scenarios. Users should be aware of this behavior when opting out of Redis.

This is still a pre-release version. While functionality is stable, further improvements and features may come in future iterations.

Foundry CLI 0.1.1 – Genesis

This release of Foundry CLI focuses on improving code quality and documentation for a smoother experience.

✔ Fixed all compiler warnings for cleaner builds
✔ Updated README to include instructions for chmod on Linux/macOS, ensuring executables can be run without permission issues
✔ Cross-platform support maintained (Windows, Linux, macOS)
✔ Self-contained binaries for easy setup
✔ Project scaffolding automation

This is still a pre-release version. While functionality is stable, further improvements and features may come in future iterations.

Foundry CLI 0.1.0 – Genesis

Genesis is the first experimental release of Foundry CLI.

✔ Cross-platform (Windows, Linux, macOS)
✔ Self-contained binaries
✔ Project scaffolding automation

This is a pre-release version and may change in future iterations.