Node.js in Shared Hosting
When you host an Internet app on our advanced cloud website hosting platform and you would like to try out Node.js, you will be able to add it to your account irrespective of the shared hosting
plan that you are using. This can be done through the Upgrades section in the Hepsia Control Panel and you’ll be able to use Node.js in no more than a couple of minutes after you add this upgrade to your account. You’ll be able to choose the number of instances that you would like to add to the account – one instance means that one app will be using Node.js. In the new section that will show up in the Control Panel, you can insert the path to the .js file in your hosting account and choose if the file in question will be accessible via the shared IP of the server or via a dedicated one. Our platform will also designate a port number for the connection. You will be able to turn off or to reboot each instance independently, if necessary.
Node.js in Semi-dedicated Hosting
With a semi-dedicated server
from our company, you can make use of all the benefits that the Node.js event-driven platform is offering, as it’s is included with all our semi-dedicated packages and you are able to add it to your semi-dedicated account with several clicks from the Hepsia web hosting Control Panel – the semi-dedicated account management tool that is included with each and every semi-dedicated server. If you would like to use Node.js for multiple web-based applications, you can choose the number of instances that the platform will use when you’re adding this service to your plan. Then, you’ll have to indicate the location of the .js file in your semi-dedicated account for each instance. You can do this in the new menu that will show up in the Hepsia Control Panel after you order the upgrade and in the meantime, you can also select whether the path to the specific application should go through a dedicated IP address – in case you have one, or through the physical server’s shared IP. Each and every instance that you activate can be restarted or removed independently and you can see the output of your apps with only a couple of clicks of the mouse.
Node.js in VPS Hosting
You can activate Node.js with any of the VPS hosting
that we’re offering if you choose Hepsia as your Control Panel. The Node.js platform will have its very own section where you can configure it with a few mouse clicks even if you have no experience with such a software platform, as Hepsia is very intuitive and easy to navigate. All it takes to activate a new Node.js instance is to specify the folder path to the .js file that will use the Node.js platform and to choose the IP that will be used to access it – a dedicated IP or your Virtual Private Server’s shared IP address. A randomly generated access port will be selected automatically too. There won’t be any constraints on the number of the Internet sites that can use Node.js at the same time, so you can use our Virtual Private Servers for plenty of sites and enjoy an astonishing performance. Quick-access menus in the Hepsia Control Panel’s Node.js section will permit you to start, to discontinue or to reboot any instance separately and to view their output.
Node.js in Dedicated Web Hosting
Node.js is included with all dedicated web hosting
on which our custom-developed Hepsia Control Panel is installed. The latter offers a very simple and easy-to-use graphical interface, so even if you’ve never worked with the Node.js platform before, you will be able to take advantage of its true potential in only a few simple steps. Once you’ve uploaded the app’s content, you will have to insert the folder path to the particular .js files that will use Node.js and to pick the IP address that they’ll use (shared or dedicated), whereas our system will assign a random port that will be used to access these files. There isn’t any limit on the total number of instances that you can set up and run simultaneously and you will exert full command over them from the Hepsia Control Panel – you’ll be able to get new ones or to terminate/restart existing ones, to revise the output log for each app, etc.