In this article, we’ll explore the key tools and features the platform provides to ensure top-notch Node.js hosting<\/a>.<\/p>\n Refer to the table of contents below to quickly locate the information you need in the guide:<\/p>\n To launch your Node.js application, start configuring the necessary environment with the user-friendly Topology Wizard<\/strong>. Navigate to the Node.js<\/strong> tab, choose the appropriate engine version for your application server, and include any other required software stack<\/a>. You can also tweak additional settings, like the number of cloudlets and nodes, and configure Public IPv4 and IPv6 addresses as needed.<\/p>\n Currently (as of this writing), the following Node.js versions are supported:<\/p>\n You can pick the Node.js version<\/a> you need when setting up a new environment, and you can also change it for an existing one if necessary.<\/p>\n The platform streamlines the deployment of managed NodeJS application servers by offering several options:<\/p>\n For further details on deploying Node.js applications, refer to the following resources:<\/p>\n To make things easier, each NodeJS application server includes a built-in development tool called the Package Manager<\/a>. This tool standardizes and automates tasks like installing, updating, configuring, and removing software.<\/p>\n NodeJS supports two types of package managers:<\/p>\n By default, NodeJS uses the npm package manager, but you can switch to yarn if needed. To do this, go to the container variables<\/a> frame and set the PACKAGE_MANAGER<\/strong> value to either npm or yarn.<\/p>\n Process managers<\/a> are essential for controlling the lifecycle of applications, monitoring active services, and ensuring the smooth operation of projects. For the NodeJS stack, our platform supports several process managers:<\/p>\n Users can select their preferred process manager during container redeployment<\/a> or by setting the PROCESS_MANAGER<\/strong> variable<\/a> to forever, npm, or pm2. A container restart is required for the new settings to take effect.<\/p>\n You can easily enhance your Node.js application by assigning it a custom domain name in place of the default one. Depending on your environment setup, you have two options:<\/p>\n Additionally, you can seamlessly redirect traffic between different environments\u2014such as directing users to a newer version of your application without any downtime\u2014by using the domain swap feature or the SwapExtIps API\/CLI method.<\/p>\n The platform automatically allocates the precise amount of RAM and CPU your nodes need based on the current load, so you don’t have to adjust anything manually.<\/p>\n This ensures you only pay for what you use, saving you both money and time by removing the hassle of managing load adjustments or making architectural changes.<\/p>\n Simply set the maximum number of cloudlets<\/a> (each cloudlet equals 128 MiB of RAM and 200MHz of CPU) for your NodeJS application server, and the platform takes care of the rest.<\/p>\n For more details, please refer to the documentation on automatic vertical scaling<\/a>.<\/p>\n To scale your NodeJS application servers, access the topology wizard and use the +\/- buttons in the Horizontal Scaling section to set the desired number of nodes. You can choose the scaling mode:<\/p>\n The maximum number of servers of the same type within a single environment layer is determined by your hosting provider, typically limited to 16 nodes. This limit can be increased by contacting support.<\/p>\n For proper request distribution, a load balancer<\/a> is automatically added when you scale your NodeJS servers. For more information, refer to the horizontal scaling<\/a> documentation.<\/p>\n To set up special tunable triggers for adjusting the number of nodes based on application load, navigate to Environment Settings > Monitoring > Auto Horizontal Scaling<\/strong>.<\/p>\n Here, you can specify the resource type to be monitored (CPU, RAM, Network, Disk) and define the exact conditions for scaling.<\/p>\n\n
Node.js Environment Hosting<\/h2>\n
![\"Create](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/06\/Create-Environment.png\" "\\"Create")
<\/a><\/p>\nNode.js Versioning<\/h2>\n
\n
![\"Node.js](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/06\/Node.js-Stack-Versions.png\" "\\"Node.js")
<\/a><\/p>\nNode.js Application Deployment<\/h2>\n
\n
![\"Application](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/06\/Application-Deployment.png\" "\\"Application")
<\/a><\/p>\n\n
Node.js Package Managers<\/h2>\n
\n
![\"Container](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/06\/Container-Variables.png\" "\\"Container")
<\/a><\/p>\nNode.js Process Managers<\/h2>\n
\n
Domains Management<\/h2>\n
\n
![\"Domain](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/06\/Domain-Management.png\" "\\"Domain")
<\/a><\/p>\nAutomatic Vertical Scaling<\/h2>\n
![\"Automatic](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/06\/Automatic-Vertical-Scaling.png\" "\\"Automatic")
<\/a><\/p>\nManual Horizontal Scaling<\/h2>\n
\n
![\"Manual](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/06\/Manual-Horizontal-Scaling.png\" "\\"Manual")
<\/a><\/p>\nAutomatic Horizontal Scaling<\/h2>\n
![\"Auto](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2024\/06\/Auto-Horizontal-Scaling.png\" "\\"Auto")
<\/a><\/p>\n