Python Selector
Create and manage supported Python web applications.
1Overview
Python Selector manages Python application runtimes where the account package and server runtime allow them.
2Before you begin
User-panel actions affect only resources owned by the signed-in hosting account. This is an advanced task; schedule it carefully and keep a rollback path.
3Step-by-step workflow
Open Python Selector, create the application, choose the registered domain, upload project files, configure the entry point and interface, install approved dependencies, then deploy and test the health result.
- Open Python Selector and check which runtime is available for your account.
- Prepare the project source, dependency file, and supported WSGI or ASGI entry point.
- Choose Create application and select a domain owned by your account.
- Set its root directory, runtime, entry configuration, and working directory using the form.
- Upload or connect the source and add the required environment values privately.
- Install dependencies into the managed application environment.
- Start or Deploy the application and inspect its startup log.
- Open the public URL and test a normal page and any database-backed function before closing the task.
4Practical example
Example: a Flask application needs its application entry point and dependencies; copying a Python source file into a public web folder does not by itself start a managed Python website.
5Verify the result
Validate the outcome from the affected website, mailbox, application, or client connection after the panel reports success.
- Confirm the process is healthy and the public route responds.
- Check application logs for import, dependency, or permission errors.
6Common problems and what to check
A required Python version is missing: ask the provider to check the supported runtime inventory.
An import fails: confirm the dependency is installed in this application environment and the module path is correct.
The URL returns a gateway error: inspect startup, entry point, listening configuration, and logs before restarting repeatedly.
7Security, impact, and rollback
Use a project-local dependency file and keep secrets in the managed environment configuration. Test changes before restarting a production application.