Node.js in Shared Hosting
When you host an Internet app on our cutting-edge cloud platform and you’d like to try out Node.js, you will be able to add it to your web hosting account irrespective of the shared hosting package that you are using. You can make this via the Upgrades menu in the Hepsia Control Panel and you’ll be able to take advantage of Node.js in no more than several minutes after you add this feature to your account. You will be able to select the number of instances that you wish to add to your account – one instance means one application using Node.js. In the new section that will show up in the Control Panel, you can type the path to the .js file in your hosting account and select whether the file in question will be accessible through the shared IP of the server or through a dedicated IP. Our system will also set a port for the connection. You will be able to stop or to reboot each instance separately, in case it’s needed.
Node.js in Semi-dedicated Hosting
With a semi-dedicated server from us, you can use all the advantages that the Node.js event-driven platform is offering, as it’s available with all our semi-dedicated hosting packages and you are able to add it to your account with a few clicks from the Hepsia web hosting Control Panel – the semi-dedicated account management tool that comes with every semi-dedicated server. If you would like to use Node.js for multiple web-based applications, you can choose the amount of instances that the platform will use when you are adding this feature to your package. After that, you will need to specify the path to the .js file in your account for each instance. You can do this in the new section that will appear in the Hepsia Control Panel after you add the upgrade and during the process, you can also select if the path to the particular app should go through a dedicated IP – in case you have one, or through the physical server’s shared IP. Each instance that you activate can be restarted or deactivated separately and you can view your applications’ output with just several mouse clicks.
Node.js in VPS Web Hosting
Node.js is offered as standard with each and every virtual private server that is ordered with the Hepsia website hosting Control Panel and imposes no restrictions in regard to the number of websites that can use it at any particular time. This makes our VPS plans an optimal choice for setting up numerous real-time apps and for making the most of them. The Hepsia Control Panel is intuitive enough even for persons without any previous experience, so if you would like to activate Node.js for any application, it will not take more than several mouse clicks to make this. You will only have to specify the path to the specific .js file and to choose if Node.js will use the physical server’s shared IP or a dedicated IP. Our platform will also designate a certain port number that will be used to access the .js file. Right after that, you’ll be all set and ready to take advantage of the full potential of your real-time apps. Hepsia will enable you to check the apps’ output and to reboot or to shut down any of your instances using quick-access controls.
Node.js in Dedicated Servers Hosting
Node.js comes with all Linux dedicated servers hosting on which our custom-built Hepsia hosting Control Panel is installed. The latter has a rather simple and user-friendly graphical interface, so even if you haven’t worked with the Node.js platform before, you will be able to take advantage of its full potential in just a few easy steps. Once you have uploaded the app’s content, you’ll have to insert the path to the specific .js files that will use the Node.js platform and to pick the IP which they will use (dedicated or shared), whereas our system will allocate a random port that will be used to access the files in question. There’s no limit as to the total amount of instances that you can activate and use simultaneously and you’ll exert total control over them through the Hepsia Control Panel – you will be able to set up new ones or to stop/restart existing ones, to revise the output log for each app, etc.