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 stable Node.js 26 RPMs for CentOS Stream 10 EPEL on x86_64. Read package metadata and signed release records. Inspect the published runtime image and read installation guides.
Use Node.js 26 or later and npm 12 or later. Use Docker Compose to run the container locally.
Run npm ci from the repository root. See local usage for repository data requirements.
Follow the end-user documentation index to run the site or use its pages and HTTP endpoints. Read release notes for version history.
Read AGENTS.md for development requirements. Read specifications before changing repository rules.
Run npm test for full validation. Run focused tests with npm test -- tests/path/to/example.test.mjs.
Use the troubleshooting guide to resolve startup, readiness, and content problems.
Attach published repository data as read-only. Keep credentials, private content, and runtime state outside Git.
See the configuration reference for environment variables, defaults, and runtime behavior.
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 public/assets/ into its static content directory. See the web application guide for asset and route details.
Assemble the static site as described in local usage, then run npm start to listen on 0.0.0.0:7100.
Run npm run build to create browser assets in dist/. The container builds and serves those assets with the page templates.
The public image is ghcr.io/eliware/nodejs-http. The workflow publishes a version tag that matches package.json. Publication does not deploy the application. See container operations for local builds.
For help, questions, or to chat with the author and community, visit:


