Node.js HTTP repository and web frontend.
- Features
- Requirements
- Setup
- Usage
- Development
- Testing
- Troubleshooting
- Security
- Configuration
- Operations
- Routes
- Assets
- Development server
- Build
- Deployment
- Support
- Links
- License
Browse published Node.js 26 RPMs for CentOS Stream 10 EPEL on x86_64. Read release metadata, installation instructions, and project articles.
Use Node.js 26 or later and npm 12 or later. Use Docker Compose for the container workflow.
Run npm ci from the repository root. See local usage for runtime data requirements.
Follow the end-user guide to run the website, configure repository data, or use its HTTP endpoints. Read release notes for version history.
Read AGENTS.md for required development and validation practices. Read specifications before changing project rules.
Run npm test for full validation. Run focused tests with npm test -- tests/path/to/example.test.mjs.
Use the troubleshooting guide to find startup, readiness, and content problems.
Set the repository path as read-only. Keep credentials, private content, and runtime state outside Git.
See the configuration reference for environment variables and defaults.
See local usage for startup and container commands. See metadata integration for readiness requirements.
See HTTP routes for pages, repository files, health checks, and API behavior.
The image copies website templates and public/assets/ into its static content directory. See web application for path details.
Run npm start to start the local server. Set PUBLIC_DIR when the repository content is outside public/.
Run npm run build to create the browser bundle in dist/. The production container serves its pages from templates.
See container operations. The GHCR workflow publishes version-tagged images. Publication does not deploy the application.
For help, questions, or to chat with the author and community, visit:


