Node.js in Cloud Hosting
When you host an Internet app on our cutting-edge cloud platform and you wish to try out Node.js, you will be able to add it to your account regardless of the cloud hosting package that you use. This can be done from the Upgrades section in the Hepsia hosting Control Panel and you will be able to use Node.js in no more than a couple of minutes after you add this service to the account. You can choose the number of instances that you wish to add to the account – one instance means one application using Node.js. In the new section that will appear in the Control Panel, you can include the path to the .js file in your web hosting account and choose if that file will be reachable via the shared IP of the physical server or via a dedicated IP. Our platform will also assign a port number for the connection. You will be able to deactivate or to restart each instance separately, if it is required.
Node.js in Semi-dedicated Servers
With a semi-dedicated server from our company, you can use all the advantages that the Node.js event-driven platform is offering, since it is available with all our semi-dedicated server plans and you’re able to add it to your semi-dedicated account with a couple of mouse clicks from the Hepsia web hosting Control Panel – the management tool that is included with every semi-dedicated server. If you wish to employ Node.js for multiple web applications, you can choose the number of instances which the platform will use when you’re adding this feature to your semi-dedicated plan. Then, you’ll have to indicate the path to the .js file in your account for each instance. This can be done in the new menu that will appear in the Hepsia Control Panel after you order the upgrade and in the meantime, you can also select if the access path to the given app should go through a dedicated IP address – if you’ve got one, or through the physical server’s shared IP. Each instance that you add can be restarted or stopped independently and you can view the output of your apps with just a couple of clicks.
Node.js in VPS Servers
All VPS servers that are ordered with our in-house built Hepsia hosting Control Panel include Node.js by default and you can take advantage of the platform for each script-powered app that you run on the Virtual Private Server. As we have not imposed any restriction on the number of Node.js instances that you can use, you can make full use of the power of our VPSs and combine it with the full potential of Node.js. The configuration is done through the Hepsia Control Panel’s easy-to-work-with, point ‘n’ click interface, so even if you are not technically proficient, you won’t need to deal with any problems while working with the Node.js platform. You will only need to enter the directory path in the account to the .js file that will use Node.js and to select if it will use a shared or a dedicated IP address. What’s more, our system will also specify a port to access the file and you’ll be able to find it in the corresponding section in the Hepsia Control Panel. With just one click of the mouse, you’ll be able to check your apps’ output and to terminate or to reboot any instance hosted on the server.
Node.js in Dedicated Servers
Node.js is available with all Linux dedicated service on which our custom Hepsia hosting Control Panel is installed. The latter has a pretty intuitive and easy-to-use graphical interface, so even if you have never worked with the Node.js platform before, you’ll be able to take advantage of its full potential in just a few easy steps. As soon as you’ve uploaded the application’s content, you’ll have to include the path to the specific .js files that will use the Node.js platform and to choose the IP that they’ll use (shared or dedicated), while our system will select a random port that will be used to access these files. There is no constraint as to the total number of Node.js instances that you can create and use simultaneously and you will exert complete control over them via the Hepsia Control Panel – you’ll be able to activate new ones or to remove/reboot existing ones, to check the output log for each app, and so on.