.run has no HSTS requirement of its own, but tala.run is served as if it had one: every HTTPS response of tala.run, www, talac, tazel and forum sends max-age=63072000; includeSubDomains; preload, and plain HTTP only answers the ACME challenge and otherwise redirects to HTTPS. A test checks both for every tala.run block of the three Nginx files. The redirects of the former .xyz domain keep their header.
The language now lives at tala.run. One frontend build serves three sites and picks its content from the host name: - tala.run: the home page, /docs/overview, /docs/getting-started and a new /docs/syntax, a first look at programs, comments, declarations, operators and evaluation by need, with every sample taken from the public specification. - talac.tala.run: /docs/command-line and /docs/outputs, the compiler's options, the entry rule, warnings, --build and --emit, and the record of a check. - tazel.tala.run: /docs/commands and /docs/project-file, the commands of the build system, target selection, workspaces and the project DSL. The new pages are written in all four locales from one content model; a test keeps code samples and option names identical across them. The header links the three sites and forum.tala.run. On a development host ?site=talac or ?site=tazel selects a site. Corrections to the existing pages: - Getting started used `go run scripts/develop.go`, `talac check -File`, `talac build -File` and `-Help`; it now uses `go run ./helpers/cmd/...`, `--emit=metadata`, `--entry=` and `--help`. - The overview no longer names the retired .vxse extension, and the project DSL is evaluated by Tazel. - Canonical URLs, Open Graph data, robots.txt and the sitemap name tala.run; talac and tazel have their own robots and sitemap files, served per host by Nginx. The notice about the move is gone: the former domain redirects instead. - The leopard mark files are called tala-mark.svg and tala.svg. Nginx: ops/nginx/tala.conf serves the three hosts, redirects www.tala.run to tala.run and every path of xsharp-lang.xyz to the same path of tala.run, and keeps viget.xsharp-lang.xyz pointing at viget.progmasoft.com; tala.run has no ViGet host of its own. ops/nginx/forum.conf serves the informational page at forum.tala.run and redirects the former forum address to it.
The language website ran a Spring Boot application on JVM 25 for two endpoints, and it was the only JVM on the server: a quarter of a gigabyte of resident memory for /api/v1/site and /health. The server already runs ASP.NET Core 10 for Progmaweb. The API is now Progmasoft.Tala.Website.Api, a minimal ASP.NET Core 10 application under the namespace Progmasoft.Tala.Website. It answers as before: /api/v1/site returns the site's own state as the same JSON, POST is not allowed there, /health answers with an empty 200, and every other path is 404. It listens on 127.0.0.1, port 5086 unless PORT says otherwise, as the Spring process did, so Nginx is unchanged. - Progmasoft.Tala.Website.slnx, Directory.Build.props and global.json set up the solution with warnings as errors, documentation comments required and NuGet lock files. - Progmasoft.Tala.Website.Api.Tests runs the endpoints in an in-memory host with xUnit v3 on Microsoft.Testing.Platform. - ops/systemd/tala-site-api.service runs the published DLL on the shared runtime from /srv/xsharp/website/current/site-api, with the hardening of the unit it replaces. - CI builds, tests, publishes and reports coverage with dotnet; CodeQL analyzes C# instead of Kotlin; Renovate watches NuGet instead of Gradle.
Invoke the framework-dependent registry status API through the installed dotnet runtime so copied immutable releases do not depend on apphost inode execution metadata surviving the SELinux staging boundary.
Move the Progmasoft mail operations baseline to its owning Progmaweb repository, remove the retired Astro account UI and duplicate identity backend, keep only the ViGet health boundary, add canonical sitemap signals, strengthen dependency CI, and adopt Patent Grant 1.1 across project-owned files.