Typical use cases
- Express.js APIs
- Node.js web backends
- runtime apps that need rebuild and restart support
Source and runtime behavior
Node.js / Express.js apps are treated as runtime applications rather than static build-only sites. Current behavior includes:- deploy
- rebuild
- restart when the runtime is healthy
App creation behavior
During app creation, the dashboard currently treats Node.js / Express.js as a managed runtime type and sets a runtime start-command path for the app configuration.Environment variables
Use app settings to configure:- API secrets
- database URLs
- service credentials
- environment-specific runtime values
Operational notes
- Node.js / Express.js apps run with plan-based runtime performance limits
- rebuild is available for runtime apps
- restart is intended for healthy deployed runtime services
Rebuild source behavior
If the app is not connected to GitHub, rebuild normally uses the current workspace contents. If the app is connected to GitHub, rebuild can be run from either:- GitHub — re-clone and rebuild from the repository source
- Workspace — rebuild from the current files in the Servbase workspace
Checklist
- Confirm app type is Node.js / Express.js
- Confirm your source contains the runtime application code expected by your project
- Confirm required environment variables are set in Servbase
- Confirm the correct branch is selected when deploying from GitHub