website/ops, branch 1.0.0The site of tala.run: a Vue frontend and an ASP.NET Core API.Redesign ViGet as a first-class Progmasoft product surface2026-09-01T11:28:16+00:00Leitwolf112026-09-01T11:28:16+00:000752b55d0095bd0b756d112e03692fe4a341c433
Separate ViGet catalogs from Progmasoft account ownership. Move login, registration, recovery, and dashboard navigation to account.progmasoft.com, document the canonical account.progmasoft.com/<Account>/dashboard route, and define each ViGet Publisher as that exact Progmasoft Account identity. Redirect legacy ViGet account routes to the account service and expose only the exact registry status endpoint while closing the retired standalone authentication and token API surface.2026-08-30T14:22:39+00:00Leitwolf112026-08-30T14:22:39+00:006420aa30d09cb0815bdf7c140ebeca6218053870
Retire registry authentication from xsharp-lang.xyz. Restrict the language host from serving the shared static /repo tree, remove the legacy api.xsharp-lang.xyz Nginx endpoint and backend host allowance, and identify the same-origin API as ViGet. Document that login, registration, and registry APIs belong exclusively to viget.progmasoft.com while preserving the dedicated legacy ViGet redirect.2026-08-30T14:14:09+00:00Leitwolf112026-08-30T14:14:09+00:00f520a23ef0066c3d1021393f1e41a49af311e109
Move ViGet to its canonical Progmasoft domain. Update registry navigation, authentication redirects, allowed hosts, Google OAuth callback documentation, and catalog identity to viget.progmasoft.com. Publish distinct honest empty-state roots for Visual X# .vipkg packages and Kotlin DSL plugin JARs without inventing unavailable package endpoints. Add production Nginx routing for the new host, preserve path and query strings through permanent redirects from viget.xsharp-lang.xyz, retain both ACME renewal surfaces, and exclude reproducible local publish output.2026-08-30T14:08:01+00:00Leitwolf112026-08-30T14:08:01+00:004bdd99b35493631aa4171753aa66d208c018f320
Transfer all project-owned website sources and operations files to Progmasoft copyright ownership under AGPL-3.0-or-later, add the shared defensive Progmasoft patent grant with SPDX and REUSE coverage, preserve third-party licenses, and align notices, package metadata, authentication, mail, deployment, branding, and repository documentation with the current ViGet service2026-08-29T08:01:03+00:00Leitwolf112026-08-29T08:01:03+00:00178f97b44da88d8653d1f942a993d06aad9b48cf
Remove the retired Java catalog host2026-08-28T15:58:48+00:00Leitwolf112026-08-28T15:58:48+00:00054cf32141cc8ec5ec0b7db0e17c676e60638ca1
Move transactional mail identity to Progmasoft infrastructure2026-08-28T15:45:11+00:00Leitwolf112026-08-28T15:45:11+00:00397a80b245a235ae0e3958787273ed5cdd61acf1
Provision the support mailbox boundary with reproducible Postfix inbound delivery, Dovecot IMAPS, authenticated STARTTLS submission, sender ownership enforcement, SELinux Maildir policy, and certificate renewal hooks2026-08-20T16:55:17+00:00Leitwolf112026-08-20T16:55:17+00:000c46a64597e252db545334381ee73f6ed8ef4bf9
Route java.xsharp-lang.xyz to its retained deprecated catalog instead of the main homepage by adding a dedicated TLS nginx virtual host with the existing certificate, shared immutable frontend assets, repository security headers, read-only static routing, and explicit deployment documentation2026-08-13T21:00:25+00:00Leitwolf112026-08-13T21:00:25+00:002804c141aacf27d2e4ca381a39b4ffa2ea36c6c8
Make the production deployment reproducible from the website repository: run the API under the static non-login xsharp_web account used by PostgreSQL peer authentication, document the passwordless Unix-socket database boundary and closed firewall posture, and record the OpenDKIM tools, private-key ownership, parent-directory traversal, and SELinux requirements discovered during the clean AlmaLinux deployment.2026-08-09T22:18:12+00:00Leitwolf112026-08-09T22:18:12+00:000ea6b8d5db87cc03dbb2583f9b870dcc19debe59