Skip to content

Conversation

alekskjo
Copy link
Member

Summary

  • add a self-hosted frontend quality gate for pull requests
  • validate and deploy only pushes to main
  • add root-owned deployment, rollback, systemd and sudoers templates
  • publish through atomic release symlinks while retaining the previous release
  • document the security boundaries and deployment model
  • fix the favicon path for the /project2 base path

Security

  • the Project 2 runner uses a separate non-login account
  • the runner cannot write to the production directories or read the deploy key
  • its only elevated command starts one fixed deployment service with no arguments
  • the deploy service independently fetches and verifies origin/main
  • Project 1 paths, users and services are not changed
  • no credentials or environment values are committed

Local verification

  • npm ci
  • npm run format:check
  • npm run lint
  • npm run test — 8 tests passed
  • npm run build
  • shell syntax and Git diff checks

The VM installation and end-to-end deployment will be verified before merge.

Closes #46

@alekskjo alekskjo requested a review from a team as a code owner October 11, 2026 16:12
Copy link
Member

@erikbsa erikbsa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. The deployment setup is clearly documented, the frontend quality checks pass, and the VM deployment has been tested. Approved.

@erikbsa erikbsa merged commit 190f00b into main Oct 11, 2026
1 check passed
@erikbsa erikbsa deleted the ci/automated-frontend-deployment branch October 11, 2026 18:51
Sign in to join this conversation on GitHub.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Set up automated frontend deployment to Apache
2 participants