outline

This interface allows you to deploy applications to the Phusion Passenger® application server. The Phusion Passenger server functions as a process manager, reverse proxy and provides operating tools to users.

This interface works on servers running Apache and Nginx.

Important :

The hosting provider must use Feature Manager interface of WHM Select Application Manager ( Application Manager ) feature and then Install one of the Apache modules .

• ea-ruby24-mod_passenger
• ea-ruby27-mod_passenger

Ruby 2.7 is not compatible with systems running CentOS 6. CentOS 7 supports both Ruby 2.4 and Ruby 2.7.

If your system runs CentOS 8, only Ruby 2.7 is available.

If necessary, the provider must also install the following packages:

• ea-apache24-mod_env — This module allows you to set environment variables for your application in your application configuration.
• ea-nodejs10 — This module supports NodeJS applications.
• python — Install the appropriate version of python for your application.

Note :

The application manager uses /usr/bin/python3 by default if it exists. If does not exist , the application manager uses /usr/bin/python by default. Basically, if you want to use a different version, add the path to your preferred version with the following command:

echo -n /path/to/python > /etc/cpanel/ea4/passenger.python

Please contact your hosting provider if you require this feature.

application

This table contains the following information:

• Name (Name) — The name of the application.
• Domain (Domain) — The domain of the application.
• Path (Path) — The file where the application's source code resides, relative to your home directory.
• Status (Status) — Whether the application is enabled or disabled.
• Actions (Actions) — Use the entries in this column to perform the following actions:
• Edit (Edit) — Edit the application.
• Register Unregister (Unregister) — Unregisters the application.
• Dependencies Enable (Enable Dependencies) —The application's Node.js package manager (npm) Check dependencies and install if necessary.

Creating an application

You must create an application before registering it with the Application Manager (Application Manager) interface. For example, you can do one of the following:

• Our Git Version Control interface to GitHub Clone an existing application from cPanel > > Home (Home) > > Files (Files ) > > Git™ Version Control (Version Control )).
• Create a new application on the server. Please read the following article for an example of how to do this:
• How to install Redmine web application
• How to install a Python WSGI application
• How to install a Node.js application

Caution : Anything you make to this interface is Application Manager (Application Manager) It doesn't work as a feature.

• cPanel's Ruby on Rails interface ( cPanel > > Home > > Software > > Ruby on Rails ).
• cPanel's RubyGems interface ( cPanel > > Home > > Software > > RubyGems ).
• Module Installers in WHM Ruby Gem Installer Section ( WHM > > Home > > Software > > Modules Installers (Module Installers) ).

We plan to remove these interfaces in future cPanel & WHM versions.

Register the application

This feature configures new applications with the most recent version of Ruby on your system. The installed version of Passenger determines which version of Ruby your system uses. You cannot install more than one version of Passenger.

Existing applications will not change their Ruby version. If you uninstall the Ruby version of your application, the application will no longer function.

To register your application, follow these steps:

1. Click Application Register (Register Application) . A new interface will appear.

2. Enter a name for the application in the Application Name (Application Name) text box.

3. From the Domain menu, select the primary domain, add-on domain, or subdomain where you want to deploy the application.

4. In the Base Application URL (Base Application URL) text box, enter the base URL for the application. After registering the application, enter this URL in your web browser to access the application.

5. In the Application Path (Application Path) text box, enter the path to the source code directory relative to your home directory.

6. Select a deployment environment. This sets up the server environment on which the application runs.

• If you are still developing your application, click Development (Development) .
• When you are ready to deploy and use your application, click Production (Production) .

1. To add an environment variable, in the Environment Variables section click Add

2. Click Deploy ( Deploy ).

environment variables

Note : To add environment variables, the system administrator must install the ea-apache24-mod_env RPM Apache module.

Environment variables allow your application to configure the processes it runs on multiple systems. The Environment Variables (Environment Variables) table contains the following information:

• Variable Name (Variable Name) — The name of the environment variable.

Important : Environment variable names must meet the following criteria:

• The name can only contain letters, numbers, underscores, and dashes.
• The name must have 256 characters or less.
• The name cannot start with a number.
• Value (Value) — The value of the environment variable.

Important : Environment variable values ​​must contain no more than 1024 ASCII-printable characters.

• Actions (Actions) — Use the items in this column to perform the following actions:
• Edit (Edit) — Edit an environment variable.
• Register Unregister (Unregister) — Deletes an environment variable.

For more information about environment variables, refer to Phusion Passenger's Environment variables document. do.

Adding environment variables

To add an environment variable to your application's configuration, follow these steps:

1. In the Environmental Variables section, click Add Variable .

2. Enter the name of the variable in Environment Variable Name text box in the Variable Name column.

3. Enter a value for the variable in Environment Variable Value text box in the Value column.

4. Click Save in the Actions column.

Editing the application

To edit your application's configuration file, follow these steps:

1. In the Applications table, find the application you want to edit.

2. In the Actions column, click Edit . A new interface will appear.

3. Make changes as desired.

4. Click Deploy ( Deploy ).

Deregistering an application

Important : Unregistering an application removes it from the list and deletes its configuration files. Applications are not deleted.

To deregister an application, follow these steps:

1. In the Applications table, find the application you want to unregister.

2. Click Unregister . A confirmation message will appear.

3. Click Register Unregister (Unregister) to completely unregister the application. A success message appears.

 

 

View original text: Application Manager