Confirm the plan supports Python and a production WSGI integration. Identify the package path, factory name, virtual environment and required environment values.

1. Install the reviewed dependencies into the application virtual environment. Keep the project and private configuration outside the public static-file directory.

2. Create the WSGI entry point required by the hosting integration. Import the actual factory and create the application object, using the callable name expected by the panel or WSGI server.

3. Load production configuration before extensions or routes that depend on it are initialised. Avoid development-only database URLs and debug settings.

4. Start the app through the supported production WSGI server or panel control. Use the platform-supported process manager rather than an interactive development server.

5. Configure static files, HTTPS proxying and private error logs. Restart the application through the same supported control after deployment.

Suppose the project package is named customer_portal and exports a no-argument create_app factory. A hosting integration that expects a callable named application can use this small WSGI entry file in the private project directory.

from customer_portal import create_app

application = create_app()

Replace the package and factory signature with the actual project values. Configure the panel or WSGI server to load this file using the application’s virtual environment and production variables. The factory should load required settings before initialising database and other extensions. The two-line adapter does not configure a process supervisor by itself.

Expected result: A clean service restart loads the application without an interactive shell. Test both a simple page and a route using an extension; a successful import alone does not prove that the production database or mail configuration is correct.

Request a public route, a route using a configured extension and a database-backed operation. Confirm the app restarts cleanly without the original SSH session.

An import error often means the wrong working directory, missing package or incorrect virtual environment. A factory argument error needs the actual factory signature checked.

• Configuring trusted proxy headers for Flask
• Setting up a production Flask error log
• Using a Python virtual environment for each application
• Managing Flask sessions and secret key rotation

• Flask application factories
• Flask deployment