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
- Merge remote-tracking branch 'origin/main' into ci/docfx
- Merge pull request #16 from Progmasoft/feature/hebrew-locale
- Merge remote-tracking branch 'origin/main' into ci/docfx
- Merge remote-tracking branch 'origin/main' into feature/hebrew-locale
- Merge pull request #18 from Progmasoft/ci/audit-braces-exception
- Accept the unfixable braces advisory in the dependency audit
- Revise the Hebrew wording
- Add a DocFX documentation gate for the API
- Add Hebrew and follow the browser language by default
- Merge pull request #15 from Progmasoft/feature/instant-locale-switch
- Update Next.js and override brace-expansion for security advisories
- Switch language in place and add Russian
- Harden Progmaweb account API and CI coverage credentials
- Add Progmaweb issue forms
- Add Progmaweb frontend tests and full-stack security and coverage workflows
- Add Progmaweb issue templates for account ViGet and corporate web reports
- Prevent Google account pre-hijacking and unsafe email-based identity merging by persisting the provider subject, indexing it independently, rejecting unverified password-account collisions and email races, reconciling only identical Google identities, and covering both service-level concurrency and the protected external-auth callback path.
- 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.
- Extend Progmaweb dark-theme and German localization coverage across account, authentication, recovery, and dashboard routes; localize page metadata and OAuth feedback; expose persistent preference controls in dashboard states; and apply saved themes before first paint.
- Describe Progmasoft accurately as an open-source organization across public web surfaces
- Treat intentional Next.js shutdown as successful
- Make Progmaweb API activation SELinux-stable
- Harden Progmaweb identity, localization, and operations
- Add explicit patent-grant applicability and preserve vested rights, replace ambiguous combination examples with a closed standalone-effects list, define future-controlled Essential Claims against a concrete recipient date, use only the defined Specified Combination term, and make the otherwise-irrevocable license subject solely to express prospective automatic termination
- Narrow the Progmasoft Patent Grant combination scope by defining Specified Combination as a particular integration identified unambiguously in public Progmasoft technical documentation, preserve future controlled patent claims, and state that general compatibility language, examples, published interfaces, SDK availability, or distribution alone do not expand the patent grant
- 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.
- Make the Progmasoft Account name the explicit ViGet publisher identity. Show the exact shared name in account discovery and dashboard views, document that ViGet does not create a second publisher identity, and retain case-preserving canonical account coordinates.
- Align Progmasoft account navigation with the canonical ViGet domain. Document account.progmasoft.com/<Account>/dashboard as the stable account dashboard route and update company and account surfaces to link to viget.progmasoft.com instead of the retired xsharp-lang.xyz registry host.
- 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
- Preserve the canonical account host across the internal Next.js rewrite by preferring the trusted X-Forwarded-Host value supplied by the dedicated Nginx proxy. This prevents the rewritten /account request from being misclassified as a corporate localhost request and eliminates the account root redirect loop while retaining the public-host isolation rule. Verified Prettier, ESLint, route generation, TypeScript, and the production frontend build.
- 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.
- 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.
- Adopt the Progmasoft brand language in the white Microsoft-style site header: replace the improvised gradient P badge with a crisp four-panel mark using the canonical palette, simplify the wordmark treatment, and separate the Account product label without embedding an oversized raster logo.
- Correct the production Next.js service path for pnpm monorepo standalone output: run the generated apps/web/server.js beneath the preserved standalone module root and document the matching static-asset placement.
- 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.
- Initialize Progmaweb 1.0.0 corporate and account platform: add a responsive Next.js corporate site without Visual X# compiler-pipeline content, host-aware account routes, registration and dashboard UX, an ASP.NET Core authentication API with account policies, password hashing, secure sessions, rate limiting and security headers, integration tests on Microsoft Testing Platform, locked dependency graphs, reproducible local orchestration, and separate frontend, backend and security workflows.