progmaweb/apps/web/tests/viget-plugins.test.mjs, branch feature/remove-xide The site and account service of Progmasoft: a Next.js frontend and an ASP.NET Core API. Show the Tazel plugins of ViGet, open the Gradle catalog, and route their files 2026-10-29T09:32:23+00:00 Leitwolf11 2026-10-29T09:32:23+00:00 3d1c6d52b830d201a68b0440a8a81c13b74c8b92 The API of the previous commit holds the catalog; this adds what people and Tazel reach. Pages: - /dslplugins/tazel lists the published plugins, read from the API on its loopback address, and says when there is none. - /dslplugins/tazel/<Publisher>/<Name> is the page of a plugin: its description, publisher, latest version, license, authors, homepage and repository, the plugins block that uses it, and every version with its date, plugin API, size, SHA-256, yanked mark and JAR. - /dslplugins/gradle opens the Gradle catalog. It only lists: Gradle takes com.progmasoft.tazel.plugin from the Gradle Plugin Portal. - The availability note says that Progmasoft publishes first and every account later. Texts are in the four languages of the site. Nginx (ops/nginx/progmaweb.conf): - On viget.progmasoft.com, index.json of a plugin goes to the API and the JARs come from /srv/viget/files with immutable caching; /api/ stays closed. - maven.progmasoft.com serves /srv/maven, whose /tazel holds tazel-api. ops/README.md describes the directories, their SELinux labels, the publish and yank commands, and how a release of Tazel copies the API into the Maven repository. Tests cover the texts in every language, the plugins block, the Gradle list, and that a page asks the API only for identifiers. 
The API of the previous commit holds the catalog; this adds what people and
Tazel reach.

Pages:
- /dslplugins/tazel lists the published plugins, read from the API on its
  loopback address, and says when there is none.
- /dslplugins/tazel/<Publisher>/<Name> is the page of a plugin: its
  description, publisher, latest version, license, authors, homepage and
  repository, the plugins block that uses it, and every version with its
  date, plugin API, size, SHA-256, yanked mark and JAR.
- /dslplugins/gradle opens the Gradle catalog. It only lists: Gradle takes
  com.progmasoft.tazel.plugin from the Gradle Plugin Portal.
- The availability note says that Progmasoft publishes first and every
  account later. Texts are in the four languages of the site.

Nginx (ops/nginx/progmaweb.conf):
- On viget.progmasoft.com, index.json of a plugin goes to the API and the
  JARs come from /srv/viget/files with immutable caching; /api/ stays
  closed.
- maven.progmasoft.com serves /srv/maven, whose /tazel holds tazel-api.

ops/README.md describes the directories, their SELinux labels, the publish
and yank commands, and how a release of Tazel copies the API into the Maven
repository.

Tests cover the texts in every language, the plugins block, the Gradle list,
and that a page asks the API only for identifiers.