Application Manager and language selectors: choose the right deployment path

cPanel Application Manager and CloudLinux language selectors can expose supported application runtimes. Their availability, supported versions, entry points and process-management behaviour depend on the provider. A Node.js selector is not a PHP version manager.

Confirm the hosting model

1. Ask which runtime and integration your plan supports: Passenger, a CloudLinux selector or another supported service.
2. Check the application’s production requirements, including background workers, persistent connections and database access.
3. Choose a separate staging URL and private project directory. Serve only the intended public entry point.
4. Configure secrets through the supported protected mechanism rather than public files or Git.
5. Install locked dependencies and use the documented restart or deployment action.
6. Test health, logging, static files, routing and recovery after a restart.

Avoid unsupported assumptions

A framework’s local development server is not necessarily suitable for shared-hosting production. Running an unattended process in Terminal does not guarantee it will survive disconnects or provider limits.

Do not change an unrelated domain’s PHP configuration to repair a Node.js application. Use the logs and runtime appropriate to that application. If the project needs a persistent worker or service unavailable on the package, discuss a supported plan or VPS deployment rather than bypassing process restrictions.