Deploy a Node.js Application in UAPP
Configure the six Node.js deployment fields, select an eligible website and installed runtime, and review sandbox deployment in UAPP.
Open Node.js → Deploy Node.js App. This workflow requires the Node.js Apps feature, an account-owned eligible website and a configured installed Node.js runtime.
Deployment fields
| Field | Required selection or value |
|---|---|
| Website | Choose a website without an existing Node.js sandbox configuration. |
| Node.js Version | Choose a listed installed runtime; the configured default is selected when present in the list. |
| Startup Script | Initial value app.js. A simple filename beginning with a letter or digit, with letters, digits, underscores or hyphens in the stem, ending in .js. |
| Public Directory | Initial value public; a relative subdirectory inside the website document root. |
| Environment | Production initially, or Development. |
| Demo Application | No, I will upload the application initially, or Install a demo application. |
All fields are required. The application type is Node.js; there is no separate framework selector.
The public-directory prefix updates for the selected website. It shows the existing document root rather than changing it. Public-directory validation permits 1–253 word characters, dots, slashes and hyphens, with no leading dot/slash or trailing dot/slash. Use a simple relative path without traversal components.
The startup field does not accept directory paths or .mjs/.cjs filenames.
Start deployment
- Back up any existing website project.
- Choose the website and runtime.
- Set the startup filename, public directory, environment and demo choice.
- Select Deploy Node.js App.
- Review website, runtime, application and environment in Review Node.js Deployment.
- Confirm and read the result.
- Open Node.js Applications, wait for deployment work and test the website.
Deployment is rejected when sandbox configuration already exists or deployment is in progress. Disabling an existing sandbox does not make it eligible for another deployment.
Your project or a demo
Choose the upload option for your own project. Supply its startup file, dependencies and application configuration. Creating the environment does not migrate an existing application or guarantee that it starts.
The demo option requests sample application files. Understand the target files and preserve an existing project before choosing it.
No eligible websites or failure
The form is hidden when there are no eligible websites or no configured installed runtimes. Check both conditions with the provider.
If task submission fails, refresh before retrying: sandbox settings may already be recorded. Do not delete an environment or start another deployment until the current state is understood.