progmaweb/apps/web/app/viget/dslplugins/tazel, branch main The site and account service of Progmasoft: a Next.js frontend and an ASP.NET Core API. Link Tazel's site at tazel.net 2026-11-06T06:44:08+00:00 Leitwolf11 2026-11-06T06:44:08+00:00 ed8dc99ef0910ae9c9797918775d18786e0a9f1b tazel.tala.run only redirects to tazel.net now. The product list and the Tazel plugin catalog link the new address directly. 
tazel.tala.run only redirects to tazel.net now. The product list and the
Tazel plugin catalog link the new address directly.
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.
Group ViGet by language and by build system 2026-10-15T15:18:50+00:00 Leitwolf11 2026-10-15T15:18:50+00:00 16b47e37e2d00b5f9bf0c83c1c03cc6a0991f1c4 viget.progmasoft.com now shows, from the top: 1. The state of the registry: what it holds today, the package format, the publisher identity and that publishing is not open yet. 2. LANGUAGES: Tala links to viget.progmasoft.com/langs/tala; C++ is a gray, disabled button that leads nowhere. 3. BUILD SYSTEM DSL PLUGINS: Tazel links to viget.progmasoft.com/dslplugins/tazel; Gradle is a gray, disabled button that leads nowhere. /langs/tala is the catalog of Tala packages and /dslplugins/tazel the catalog of Kotlin DSL plugins for Tazel, both honestly empty. /langs and /dslplugins redirect to them. The header, the footer and the sitemap link the two catalogs, and the coordinates they show begin with the catalog: /langs/tala/<Publisher>/<Name>/ and /dslplugins/tazel/<Publisher>/<Name>/. The text of the catalogs lives in lib/viget-catalogs.ts in all four locales; localization.ts is close to the size limit of a file. The two section headings are the registry's names and stay in English. The language links of the ViGet and Progmasoft pages point at tala.run. 
viget.progmasoft.com now shows, from the top:

1. The state of the registry: what it holds today, the package format,
   the publisher identity and that publishing is not open yet.
2. LANGUAGES: Tala links to viget.progmasoft.com/langs/tala; C++ is a
   gray, disabled button that leads nowhere.
3. BUILD SYSTEM DSL PLUGINS: Tazel links to
   viget.progmasoft.com/dslplugins/tazel; Gradle is a gray, disabled
   button that leads nowhere.

/langs/tala is the catalog of Tala packages and /dslplugins/tazel the
catalog of Kotlin DSL plugins for Tazel, both honestly empty. /langs and
/dslplugins redirect to them. The header, the footer and the sitemap
link the two catalogs, and the coordinates they show begin with the
catalog: /langs/tala/<Publisher>/<Name>/ and
/dslplugins/tazel/<Publisher>/<Name>/.

The text of the catalogs lives in lib/viget-catalogs.ts in all four
locales; localization.ts is close to the size limit of a file. The
two section headings are the registry's names and stay in English.

The language links of the ViGet and Progmasoft pages point at tala.run.