progmaweb
The site and account service of Progmasoft: a Next.js frontend and an ASP.NET Core API.
Clonegit clone https://git.progmasoft.com/progmaweb
mainroot / ops / nginx / progmaweb.conf
- Serve the Agenceland MCP Marketplace on agencelandmcp.progmasoft.com
- Remove ViGet; keep the accounts
- Merge main into site/license-pages
- Explain PM-SPL 1.0 on license.progmasoft.com
- Hand catch3.uk to its own site
- Serve the Catch3 site at catch3.uk
- Merge main into legal/patent-grant-notice
- Remove what is left of the former language and its site (#70)
- Name the copyright license alone in SPDX expressions
- Merge remote-tracking branch 'origin/main' into security/cloudflare-real-ip
- Rate-limit sign-in by visitor behind Cloudflare and stop forwarding h2c
- Remove Xide and ides.progmasoft.com
- Show the Tazel plugins of ViGet, open the Gradle catalog, and route their files
- Redesign progmasoft.com and add the product catalog and product sites
- Move the OAuth pages to Next.js and split the authorize host and the console
- Add Progmasoft OAuth, an OAuth 2.1 and OpenID Connect provider
- Treat progmasoft.com as an HSTS-preloaded domain
- Move the ViGet package and DSL-plugin catalogs into Progmaweb as host-aware Next.js routes, add complete en-US and German content, persistent light and dark themes, catalog-specific metadata, robots and sitemap responses, and an Nginx ownership contract for viget.progmasoft.com.
- Harden Progmaweb identity, localization, and operations
- Establish Progmasoft copyright ownership across the corporate website and account service, license all project-owned sources under AGPL-3.0-or-later, add the shared defensive Progmasoft patent grant with SPDX and REUSE coverage, preserve source-availability obligations, and align notices, npm and .NET package metadata, frontend, API, tests, deployment configuration, and repository documentation
- Activate the account.progmasoft.com production host with dedicated HTTP and TLS virtual servers, ACME-compatible certificate routing, security headers, and loopback proxy forwarding. Correct the host-aware Next.js account landing rewrite so public HTTPS termination at Nginx does not cause the HTTP-only Next listener to receive an invalid TLS connection. Verified formatting, ESLint, generated route types, TypeScript checks, production frontend build, live Nginx syntax, Cloudflare DNS publication, and the expanded Let's Encrypt SAN set.
- Separate Progmasoft production hosting from Visual X#: enable portable Next.js standalone output, add hardened loopback-only systemd services for the frontend and account API, define dedicated TLS Nginx virtual hosts with canonical www redirection and ACME handling, document immutable release activation and rollback, and remove workstation-specific tool paths from orchestration.