Node.js in Shared Web Hosting
When you host an Internet app on our leading-edge cloud hosting platform and you’d like to try out Node.js, you’ll be able to add it to your web hosting account regardless of the shared web hosting plan that you’re using. You can make this from the Upgrades menu in the Hepsia hosting Control Panel and you will be able to use Node.js in no more than a few minutes after you add this upgrade to the account. You can choose how many instances 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 specify the path to the .js file in your hosting account and select whether that file will be accessible via the shared IP of the physical server or through a dedicated one. Our system will also assign a port for the connection. You’ll be able to switch off or to restart each instance separately, in case it’s 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 platform is offering, due to the fact that it is available with all our semi-dedicated packages and you can add it to your account with a few mouse clicks from the Hepsia hosting Control Panel – the semi-dedicated server management tool that is included with each and every semi-dedicated server. If you would like to employ Node.js for multiple web-based apps, you can pick the number of instances that the platform will use when you’re adding this feature to your package. Then, you’ll have to specify the path to the .js file in your account for each instance. This can be done in the new menu that will show up in the Control Panel after you order the upgrade and in the meantime, you can also select if the access path to the particular application will go through a dedicated IP – in case you have one, or through the server’s shared IP address. Each and every instance that you activate can be rebooted or stopped separately and you can view the output of your applications with just several mouse clicks.
Node.js in VPS Servers
Node.js is included by default with each VPS server that comes with the Hepsia hosting Control Panel and involves no limitations regarding the number of sites that can use it at any given moment. This makes our Virtual Private Server packages an excellent choice for building different real-time web-based applications and for taking full advantage of each of them. The Hepsia Control Panel is intuitive enough even for persons with no previous experience, so if you want to activate Node.js for any application, it won’t take more than a couple of mouse clicks to make this. You’ll simply have to insert the folder path to the given .js file and to select whether Node.js will use the server’s shared IP or a dedicated one. Our platform will also allocate a certain port number that will be used to access the .js file. Right after that, you will be all set and ready to make use of the full potential of your real-time applications. The Hepsia Control Panel will permit you to see the output of the applications and to reboot or to delete any of your instances using fast-access buttons.
Node.js in Dedicated Servers
Node.js comes with all Linux dedicated servers on which our custom-developed Hepsia Control Panel is installed. The latter offers a very intuitive and easy-to-use interface, so even if you have never worked with the Node.js platform before, you’ll be able to unleash its full potential in just a few easy steps. As soon as you’ve uploaded the app’s content, you’ll have to insert the path to the particular .js files that will use the Node.js platform and to select the IP which they’ll use (shared or dedicated), while our system will choose a randomly generated port that will be used to access the files in question. There is no restriction as to the total number of Node.js instances that you can activate and use at the same time and you’ll have full control over them from the Hepsia Control Panel – you will be able to get new ones or to discontinue/reboot existing ones, to check the output log for each application, etcetera.