Express: Difference between revisions
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
= Express.js = | = Express.js = | ||
{{Caution| | |||
If you use Node.js, we strongly recommend that you [https://heliohost.org/dashboard/load/ monitor your site load here]. | If you use Node.js, we strongly recommend that you [https://heliohost.org/dashboard/load/ monitor your site load here]. | ||
Node apps often require a lot of server resources, and exceeding the account load limits will cause your user account to be [[:Suspension_Policy#High_Server_Usage|suspended for high server usage]]. | Node apps often require a lot of server resources, and exceeding the account load limits will cause your user account to be [[:Suspension_Policy#High_Server_Usage|suspended for high server usage]]. | ||
}} | |||
= About Express.js = | = About Express.js = |
Revision as of 17:51, 17 October 2024
Express.js
If you use Node.js, we strongly recommend that you monitor your site load here.
Node apps often require a lot of server resources, and exceeding the account load limits will cause your user account to be suspended for high server usage.
About Express.js
Express.js is a web application framework for Node.js. It provides a set of tools and features to build web applications and APIs quickly and easily. Express.js simplifies common tasks like routing, handling HTTP requests and responses, setting up middleware, and managing sessions. It is lightweight and flexible, allowing developers to structure their applications as they see fit. It is commonly used for building RESTful APIs or server-side applications.
Node.js on Plesk Uses Passenger
What is Passenger?
Passenger is a way of running Node.js, Ruby on Rails (RoR), and other applications that normally require a constantly running background process. Instead of the process always running in the background just waiting for connections, Passenger shuts it down if there are no connections. When someone visits the website, Passenger fires up the Node.js (or Ruby, or whatever language you're using) process. If another person visits the website while the Node.js process is still running, page loads will be very fast. If there are no further page hits for 5 minutes or so, Passenger kills the background process.
Why Does HelioHost Use Passenger?
It doesn't make sense to leave your car running 24/7 in front of your house just in case you need to drive somewhere so it saves you a second to start the engine. This is a massive waste of gas. Likewise, it doesn't make sense to leave Node.js sites running 24/7 just to save a second of load time in case someone needs to view the page. This is a massive waste of memory. At HelioHost, we want to ensure that the server memory is used efficiently so our servers work efficiently for the hundreds of users on our shared hosting platform.
Will Passenger Slow My Site Down?
A recent speed test on HelioHost servers showed that our app only took 177ms to load from a cold start. That's just under 1/5 of a second, roughly the amount of time it takes to blink.
How Can I Use Passenger?
By following the steps in this tutorial, Plesk will automatically use Passenger to run your Node.js application.
Can I Change the Inactivity Timeout?
No, the background process timeout is set to ensure fair resource usage for all our users and cannot be changed. If you need more control over memory management, HelioHost offers a range of VPS plans, where you can configure your settings.
Can I Prevent My Site from Sleeping?
Passenger is designed to keep our shared hosting servers running efficiently and help keep your account within the account load limits. Deliberately preventing your site from sleeping is likely to get your account suspended for high server usage.
What If My Users Cannot Wait For My Site To Load?
If your application is highly time-sensitive and every millisecond of load time matters, HelioHost offers a range of VPS plans. With a VPS, you won’t share your server with other users, so you can run any continuous process(es) that you want.
Setup
If you prefer visual guidance, we have a video tutorial available for you to watch. To follow the written instructions, please continue reading below.
Go into your project root. (If you don't have a project, you can use this example project.)
How to Setup Express.js
Your Node.js files will go into your user directory (NOT `httpdocs`):
Note: Delete the content inside `httpdocs`
If you're not using the above example, then create a new file `app.js` and put this inside:
const http = require('http'); const express = require('express'); const port = 3000; const app = express(); app.get('/', (req, res) => { res.status(200).send('Node.js is working with Express and http.'); }); // Create an HTTP server using the Express app const server = http.createServer(app); server.listen(port, () => { console.log(`Server running`); });
Create a new file `package.json` and put this inside:
{ "name": "node-test", "version": "0.0.0", "private": true, "scripts": { "start": "node app.js" }, "dependencies": { "cookie-parser": "~1.4.4", "debug": "~2.6.9", "express": "~4.16.1", "http-errors": "~1.6.3", "morgan": "~1.9.1", "pug": "^3.0.2" } }
In Plesk, go to: `Website & Domains > [domain]`
Server Setup
Upload all your files to your server. Then go to the Node.js section and set the following:
- Node.js Version: we recommend using the latest available.
- Application Root: `/` (This is the folder where you uploaded your project.)
- Application Startup File: `app.js` (The entry point of our app, use the file we created earlier.)
- Here, you're able to configure settings for your application.
Starting the Server
Once all of the above steps are done, press the `Enable Node.js` button.
Then you need to run the `NPM install` command.
Finally, you will need to wait up to 2 hours for the server to update.
Node.js application deployment can take up to 2 hours to go into effect as it requires an Apache restart. After an entire 2 hours, if your Node app is not working for you, please clear your web browser cache.
Once the Node.js application has been deployed, you should be able to visit `domain.helioho.st` in your web browser and see the text `Node.js is working with Express and http.`
Further Support
If it's been more than 2 hours, and the Node.js application still isn't working, please go back and check all of your steps again. If it's been more than a full 2 hours since your changes, and it still isn't working even after you clear your web browser cache, please make a new post in the Customer Service forum, making sure to provide your username, domain, and any error message(s) encountered.