Skip to content

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

Choose a tag to compare

View all tags
@Caio26Gualberto Caio26Gualberto released this 12 Apr 06:52
v0.2.3_Templates
3c11208

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.

Assets 3
Loading