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 / systemd / progmaweb-api.service
- Name the copyright license alone in SPDX expressions
- Harden the systemd units of the API and the web frontend
- Keep accounts and sessions in PostgreSQL
- Make Progmaweb API activation SELinux-stable
- Harden Progmaweb identity, localization, and operations
- Add secure Google sign-in to Progmasoft Account. Use the server-side authorization-code flow with an exact account-domain callback, temporary hardened external cookies, verified provider email matching, canonical Account-name creation for new users, and no separate ViGet publisher identity. Add frontend entry points, provider failure guidance, locked Google authentication dependencies, service secret injection, and backend regression coverage without committing OAuth credentials.
- 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
- Complete production activation hardening: allow the explicit loopback and canonical Progmasoft hosts used by the Next.js API proxy, and omit MemoryDenyWriteExecute only for the CoreCLR service because the .NET JIT requires managed executable mappings while all other systemd protections remain enabled.
- 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.