Atanas Korchev cf4a3feded Speed up website deploy: generate API docs from the Radzen.Blazor package ...

The Docker deploy compiled Radzen.Blazor from source (3 target frameworks
plus Sass and Terser) only to feed the API reference generator, even though
the deployed site ships the published Radzen.Blazor NuGet package. Generate
the API docs and llms.txt from that same package and drop the source build.

- Radzen.Blazor.Api: reference the Radzen.Blazor package in Release (source
  project in Debug), like RadzenBlazorDemos already does; the generator reads
  the package dll/xml.
- RadzenBlazorDemos: GenerateLlmsTxt reads the package XML in Release so the
  LLM docs keep their API descriptions.
- Dockerfile: restore for Release, drop the Radzen.Blazor source build,
  generate API pages from the restored package, set NUGET_XMLDOC_MODE=none so
  the package XML is extracted.
- Add .dockerignore to keep .git/bin/obj out of the build context.
- deploy.yml: shallow checkout (fetch-depth 1).

2026-06-24 20:25:11 +03:00

550 B

Raw Blame History

View Raw