Applications ​
Applications runs a Node.js, Python, or Ruby application on one of your domains. The wizard ships a starter page that serves immediately, so you can confirm the application is running before you put your own code there.
Overview ​
URL: /client/applications
The page sits under Software in the client navigation.
Each application belongs to one domain. A domain that already runs an application is not offered again.
Creating an application ​
New Application opens a four-step wizard.
1. Runtime ​
| Field | What to choose |
|---|---|
| Domain | The domain the application will serve. Only domains not already running one are listed. |
| Application Name | A name for the application. |
| Runtime | Node.js, Python, or Ruby. |
| Runtime Version | A version your server has installed, or the server default. |
The runtime list says what each option can actually do on this server. A runtime marked cannot be served on this server is one the web server does not support; a runtime marked needs setup by your administrator is one whose versions are not installed yet. The version field names the versions this server has.
If every runtime is marked that way, ask your hosting provider before going further. Applications run on Apache and OpenLiteSpeed; under LiteSpeed Enterprise the application would answer with a directory listing instead of starting, and the panel says so rather than letting you build something that cannot work.
2. Location ​
Where the code lives and how it starts. The application root is taken relative to your domain's folder, so you give a path inside your own space rather than a full server path.
3. Environment ​
The variables passed to the application. This is where configuration such as connection strings and API keys belongs, rather than in the code.
4. Starter application ​
A minimal application that serves a page as soon as it is created. Keep it for the first run: if the starter page loads, the domain, runtime, and startup are all correct, and anything that breaks afterwards is your own code.
Running an application ​
Each application has its own log and a restart action in the panel. Restart after changing code or environment variables; the running process does not pick either up on its own.
Over the API ​
Applications are fully covered by the client REST API: listing, creating, updating, deleting, reading the log, and restarting. That is what makes a deployment script possible without a panel session.
Related pages ​
- Domains - the domains an application can be attached to.
- File Manager - where the application's code lives.
- Error Logs - the domain's web server errors, separate from the application's own log.
- Databases - the databases an application connects to.