Create and Verify a Python App with cPanel Python Selector

If your hosting account provides CloudLinux Python Selector, its Setup Python App interface can register a Python web application with Passenger. Confirm that feature and a compatible runtime before uploading an application; ordinary cPanel access does not establish that Python hosting is included.

Prepare a compatible application

Identify the framework's supported Python version, dependencies and WSGI entry point. This workflow is for a compatible WSGI application, not a promise that any ASGI service, worker or long-running process is supported. Keep a working local or staging copy and record the application's configuration requirements.

Register it in Python Selector

Open Setup Python App and choose Create Application. Follow the CloudLinux Python Selector interface guide for the installed version.

• Select a compatible Python runtime from those actually offered.
• Set the application root and intended domain/URL path.
• Set the startup file containing the WSGI callable and the callable's name. The documented defaults are passenger_wsgi.py and application; your framework may need an adapter.
• Configure the log location and required environment variables without exposing secrets in public files.

These fields describe different things: the root is a filesystem location, the URL is the public address, and the entry point is a callable object, not an arbitrary folder or framework name.

Install dependencies and validate

Use the application's dependency file and the environment associated with this registered application. The panel can run pip installation from a configuration file; use the displayed environment instructions if working through an authorized shell. Do not install dependencies into an unrelated system Python.

Start or restart the application, then request its intended HTTPS URL. Check an application-specific response and its logs; a panel status indicator is not proof that database connections, authentication or background work succeed. Resolve import and entry-point errors before changing unrelated server settings.

Record runtime, root, URL, entry point and dependencies for recovery. If the application needs capabilities outside the offered environment, confirm another deployment model with the provider rather than assuming the panel can run it.