Node.js vs Ruby on Rails: Which to Choose

Node.js vs Ruby on Rails: Which to Choose - Plesk

Choosing between Node.js and Ruby on Rails when you select your development platform is a key decision. It will impact the way your project unfolds over time and how much server resources you’ll need. Both languages can support web applications of great complexity, but each has distinct advantages and disadvantages. Knowing these pros and cons will help you pick the optimal solution to fit your intended project.

A Quick Intro to Node.js and Ruby on Rails

What’s the background and purpose of each of these languages? Let’s take a quick look.


In short, Node.js is a runtime environment that allows you to execute server-side, what used to be essentially client-side, code. The “js” in Node.js, of course, stands for JavaScript. A scripting language that’s been in use on the client side since the late 90s.

So, Node.js, built on version 8 of the Chrome JavaScript engine, lets you execute JavaScript on a server. It was originally intended to make it easier to create push capability for real-time websites. But Node.js is an expansive platform. And it includes native modules that can manage everything from files to computing resources and security. Both PayPal and Uber use Node.js.

Ruby on Rails

Built on the Ruby programming language, Ruby on Rails ( RoR, or sometimes just “Rails”) is a fully-fledged website framework which includes everything you need to complete a website project including the ability to manage logic, routing and applications, all out of the box. These handy tools also include database integration and controllers which makes it easier to facilitate web development on an end to end basis. Popular applications running on RoR include GitHub and AirBnB.

Node.js vs Ruby on Rails: Where Node.js Wins

node js vs ruby on rails - where node js wins - Plesk

Fast Execution

node js vs ruby on rails - node js fast execution - Plesk

Node.js is best known for its speed. Partly thanks to a combo of programming centered events and programming which is not synchronised. Plus, input output that avoids blockages. All of which maximises the use of a single processor core and computer memory.

Effectively, Node.js can handle more requests at the same time, and by definition, the workload of many web servers. Node.js allows programs to keep working even the input, output demands when a server is high. Keeping app performance up no matter the load.

One Language Only

node js vs ruby on rails - node js one language only - Plesk

It’s obvious what the advantage of this point is. If you code in only one language on both the front-end and server-side, you progress quicker. Node.js came composed out of JavaScript. So, it’s easy to line up with front-end techniques to make effective second-gen web apps with less hassle. Your team can be smaller and more efficient while also delivering faster results.

Node.js is also good for Scalability

The mix of Node workers and clusters can easily create additional Node.js processes, all depending on the workload. This makes Node.js applications easy to grow. The way Node.js is designed means that what you can do is really only limited by the number of server processors you have access to. Making Node.js a good platform if you’re planning on rolling out enterprise apps.

Points to watch out for with Node.js

Points to watch out for with Node.js - Node js vs Ruby on Rails - Plesk

Efficiency when operations are CPU intensive

Node.js is great for applications which involve small, frequent and simultaneous requests. However, it can struggle with applications which create high CPU usage in each thread. Because Node.js is single-threaded. If you’re going to manipulate images and video on your server, you may find that Node.js bogs down. There are workarounds. But it adds to development time and cost.

Quality of modules and documentation

Node is flexible but this can be a problem. Sometimes modules are low-quality and the documentation on offer can be short on specs. As the developer, you have a choice of modules with Node.js. And it’s not always obvious which module is best. Choosing a template engine, for example, can take time.

So Node.js is less of an out-of-the-box solution compared to RoR. Modules can be tricky to integrate too, while also being buggy and introducing unexpected behavior for devs. It’s, therefore, key to have an experienced Node.js developer on your team who can help solve issues.

Ruby on Rails vs Node.js: Where Ruby on Rails Wins

Ruby on Rails vs Node js - Where Ruby on Rails wins - Plesk

Web Development Best Practices

Where Ruby on Rails wins: Web development best practices - Ruby on Rails vs Node js - Plesk

Rails comes with a view to create best practice for web development. The creator intended to make it easy to develop sites according to a set framework which puts convention before configuration. As such, Ruby On Rails ships with every necessary library and module. And they all implement the model, view and controller paradigm. The intention is to make web development as predictable and smooth a process as possible.

Extensive Infrastructure

Ruby on Rails advantage: extensiveinfrastructure - Ruby on Rails vs Node js - Plesk

RoR’s built for quick site development. So, it includes an integrated web server. Plus, it has a database with generators and scripts. These are powerful and hence make it easy to put together a Rails application. You can automatically put all the necessary bits and pieces a functioning Rails site requires in place. It’s absolutely great for rapid development.

Exchange/Use Database Info

You can easily migrate Rails databases. Because the model that supports the Rails database, ActiveRecord, can easily translate the differences amongst the numerous SQL interactions. Instead of writing out SQL code, users of Rails can use the Rails language to describe changes to database tables.

So, in effect, the schema being created is agnostic of the database in use. Which means you can run your Rails application in many different database environments.

Points to watch out for with Ruby on Rails

Points to watch out for with Ruby on Rails - Ruby on Rails vs Node js - Plesk

Flexibility can be an issue

Often, for every advantage, there is a matching drawback. This is the case with RoR too. Due to Rails creator’s development vision, you may feel restricted with RoR if your particular application is too unique. The Rails platform imposes a lot of authority on the developmental process. So there can come a point where adjusting RoR to fit your requirements takes up a huge amount of your time. Whereas simply starting from scratch would have been quicker.

Performance is not always optimized

Again, a positive point that can also be a negative. Because of the large number of modules in the box, RoR can seemingly bog down when running in the real world. The overall framework is heavier than alternatives, including Node.js. So it’s not so efficient at managing a barrage of requests – typical of many website applications. You can add more server instances, but these use up your memory.

Debugging can be tedious

Because of Ruby on Rails’ complexity and multiple layers, it can be difficult to troubleshoot a Ruby application. Finding an error in the mix can be very time-consuming. So if something goes wrong, perhaps compounded by your application’s custom requirements, you can find Ruby on Rails a very tedious platform to develop on.

How to pick between Node.js and Ruby on Rails

how to pick between node js and ruby on rails - Plesk

The only thing that’s clear is that neither Node.js nor Ruby on Rails provides a solution ideal for every development situation. But each environment is suited to a specific kind of task. Let’s look at the types of tasks each environment is most appropriate for.

Where Node.js works better than Ruby on Rails

By now you may have gathered that Node.js is great for applications that are real-time. And which handle a lot of concurrent requests. Under these scenarios, data constantly goes between the client and server. These Real-Time Applications (RTAs) include chat apps, applications for collaborating and video conferencing.

Because Node.js is event-based, it’s great for handling these apps. Running on a single page (known as SPAs or Single Page Applications) involves a lot of processing on the client side. The main function for the back-end under these scenarios is to just provision a REST API. Whenever you’re worried about performance and scalability, you should turn to Node.js first before you consider Ruby on Rails.

Where Ruby on Rails is preferable to Node.js

As I said before, Rails is a better solution where your applications are very CPU intensive. And where development needs to happen quickly. Because Node.js is a single-threaded environment, it cannot cope well with handling data such as images and graphics. A computation on a big dataset in Node.js can simply block all the other requests that are coming in. Hence, rendering the advantage of Node.js void.

Second, Rapid Application Development, or RAD, is an important aspect of rolling out websites too. And here, Ruby on Rails is the clear winner. You can have a prototype in short thrift, with little work, when you use Rails. Whereas just starting out on Node.js involves quite a lot of choices. As much as Node.js provides generator scripts to speed up development, it’s simply never as fast as Rails.

When you pick between the two platforms, the main points you should consider are the development speed you need, and the server performance parameters. Are you running lots of simple, concurrent requests through the application? Or more complex, CPU intensive requests? Go with Node.js for concurrency, and Ruby on Rails for CPU intensive applications.

Plesk Onyx Hosting Platform with Node.js and Ruby on Rails

Plesk Hosting Platform with Node.js and Ruby on Rails - Plesk


We think Node.js is a great open-source platform that is great for developing server-side web applications. Even though it has only been around for a few years, it’s already gathered a lot of support. We also like that it uses JavaScript. So the learning curve is relatively shallow. Meanwhile, you can get super-fast apps with Node.js.

Plesk hosting platform helps because of all the following.

  • You activate Node.js applications for your website in just a few quick clicks
  • Manage Node.js Apps easily from the Plesk panel. Including restarting and stopping applications and adding npm packages. You can also run scripts and edit the Node.js configuration files on Plesk.
  • Under Plesk for Linux, you can also install multiple versions of Node.js.

Ruby on Rails

Rails is still very popular, so we make it easy to get going with Ruby on Rails via an extension to Plesk. The extension allows users to very quickly deploy Rails apps on a domain, including the Sinatra framework. Our extension lets you do the following.

  • Enable the support of Ruby on Rails on any virtual host.
  • Pick the Ruby version you want to use on your domain.
  • Get maximum conformity for both UI and CLI calls via the rbenv utility.
  • Install gem dependencies using a UI with the Bundler tool.
  • You can edit configuration files and supply custom environment variables.

Finally, we strongly suggest that, when using Ruby on Rails, you install the tools required for building Ruby gems components. In order to easily and quickly facilitate a Ruby gem installation. These components let you relax and forget about the decency difficulties that users often experience with Ruby. Because our bundled tools automatically resolve dependencies for you.

The Admin Benefits You’re Getting with Plesk Server Control Panel

Admin Benefits of the Plesk Server Control Panel - Plesk

Web experts design hosting server control panels to help any kind of user, no matter how technically-skilled. Why? Because their goal is to help properly set up and manage websites. Instead of having to type complicated commands, users can just have a user-friendly GUI that performs actions. At the moment, the Plesk server panel is one of the most popular web hosting control panels in the world.

It has an intuitive and clear interface that everyone can find their way around. Especially true if the user has WordPress experience since the Plesk interface assumes a WordPress approach in terms of usability. Keep scrolling for details of Plesk’s core features.

Don’t have Plesk yet?

Get a Plesk Quote Try Plesk for Free

1. Easily Customizable Plesk Server Panel

Easily Customizable Plesk Server Panel - Admin Benefits of Plesk - Plesk

So why is Plesk so intuitive and simple? Because it provides the scope of all necessary tools you need to start – the right way. Essential tools that help you manage your website’s whole lifecycle. With Plesk Onyx, the latest release, you can use category pages for easy navigation while looking for the right tools.

Apart from Onyx basics, you can even customize your Server Panel with various extensions, split into categories within the menu. You’ll find the most popular ones on the main page and more extensions you may need in any of the categories. Narrow your search if you like and you can quickly add extensions in just a few clicks. Here are some favourites:

Also, you don’t have to pay for extensions you don’t need. Because Plesk designed its interface for you to only add what you use. This is how the overview is kept clean and simple within the server panel. Plesk Onyx and other latest versions also provide better support with new extensions such as Git, Node.js, Ruby, and Docker.

2. High Level Of Compatibility

High Level Of Compatibility - Admin Benefits of Plesk - Plesk

Plesk server panel supports many different operating systems, platforms and technologies. Thus multiplying its strength and contributing to the fact that most Windows Server installations use the Plesk control panel. Since cPanel and others don’t support Windows OS.

Still, the Plesk server panel isn’t limited to Windows servers only – it supports many different Linux versions too. Plesk also works with lots of different tools and platforms. Like the out-the-box WordPress Toolkit extension. This comes available and ready to use with most Plesk Onyx editions.

3. Variety of Admin Tools

Variety of Admin Tools Available - Admin Benefits of Plesk - Plesk

Administrators’ tools and extensions also include Magento, Patchman, CloudFlare CDN, and Let’s Encrypt. Compatibility with various OSs, tools, apps, and platforms allow admins to run their sites the way they see fit. Not just limiting themselves to useless or unappealing options.

Give users the ability to find what they need and add it to their control panel. You’ll ensure a clutter-free environment that’s easy to use and navigate.

4. Automation and Easy Management

Automation and simplified setup procedures are among the core benefits that Plesk brings to the table. Because server admins get to reduce the efforts and time for routine tasks when they need to.

You can install Plesk on Windows easily as it has a very intuitive GUI. It’s also easy to set up on Linux because it only requires one command to install with default settings. To set up a website using Plesk Onyx, you’ll have to go to the Domains page. First, simply click the domain name. Then choose Files > Databases > Install Apps > Install WordPress to make a brand-new website.

If you use a CMS like Drupal, Joomla or WordPress, you can create, secure and launch a site in minutes. Just drag and drop to add new content or features without having to insert a single line of code. Most extensions have one-click installation so you can set them up instantly.

You can automate server tasks by going to Tools and Resources. Then choosing Scheduled Tasks on the Tools and Settings page. Here you can schedule commands or PHP scripts too.

Moreover, you get extensions like Perfect Dashboard that give you more task automation power. For example, one-click updates for all websites on one account and automated backup integrity verifications. Or engine tests to show if any layout changes have cost you broken SEO tags, social tags, or display errors.

Who can start on Plesk Server Panel?

Various end-user groups with any level of experience can easily use the Plesk server panel. Because it has a clean and user-friendly GUI, huge compatibility potential and a large extension ecosystem. The latest Onyx release has a similar approach. Thus giving more capabilities, including tools and multi-server abilities.

Although there are administrators who still prefer working on CLI, Plesk may still save their time. And beginners get to learn quickly and get rid of the need for third-party support services.

Don’t have Plesk yet?

Get a Plesk Quote     Try Plesk for Free

PHP vs Node.js: Which is better?

Php vs Node.js

JavaScript has been around a long time and has always been at the forefront of making things happen. That is, on the front-end – handling everything browser-side. For back-end, doing the heavy server-side stuff, we used PHP. Even on some of the most popular websites worldwide. Meanwhile, Node.js has really overturned the old way of doing things. So now it’s PHP vs Node.js – who wins?

The story of Node.js and PHP

Many wonder why JavaScript was trapped in just front-end. It led to Node.js and the framework which allows JavaScript to not just run client-side, but everywhere. In this ideal world, developers could use a single language, both when programming client-side and server-side. In fact, Node.js has really taken off for a variety of reasons. And if you develop, you have an enormous amount of choices of platforms including the ultra-popular Angular JS.

PHP has also seen a huge amount of development with speed being one of the greatest benefits. At version 7, PHP has come a long way with JIT compiling a particularly popular feature of the later versions of PHP. Basically, PHP can now deliver just as quickly as Node.js and there’s also HHVM with hash which supports really cutting-edge programming techniques.

As always in technology, it’s not easy to decide what will lead the future. Sometimes there is a place for both competing technologies, sometimes it’s Betamax vs. VHS: only one will survive. But right now, we take a look at the situations where PHP serves you better, and point out the use cases where Node.js is a better choice.

Pro of PHP: Code and content together

As much as projects have different requirements for efficiency of code, logic and planning, it stays true that splitting the logic layer from the content layer is a wise choice. But do you want to spend time doing so? A PHP advantage is that it makes it easy to quickly add logic in the middle of HTML content. You can just trigger some logic by picking out a few markers in the URL, and tweak your content accordingly. Job done. And with some websites, that’s all you need.

Pro of Node.js: Everlasting power of MVC

A complex site with lots of logic snippet dispersed across pages can be difficult to manage. With Node.js you need to act in a more structured way (Model-View-Controller model). But with a complex application, structure is better for everyone. Node.js prompts you to lay code out in a way that is easy for you to maintain. And easy for a new project team member to understand. Yet, planning always takes time, and this structured approach might not be ideal under all scenarios.

PHP vs Node.js: Having variety against being up-to-date

Experienced programmers will know that an established code base is both a blessing and a curse. On the one hand, PHP provides you with a wide selection of libraries and frameworks, so you don’t have to write thousands of lines from scratch: almost every imaginable necessity has its implementation in code. However, this huge code base is not necessarily fresh or relevant. In the world of fast-moving web apps, this can be a liability.

Node.js, in contrast, offers a code base which is aware of the latest developments in web architecture. Though you may find fewer completed code chunks those which you do find will be more relevant. Besides, with Node.js you’ll find coding from fresh easy and quick because of its design. It fits into current development models, including the push for clients to do the heavy-lifting.

PHP vs Node.js: Simplicity but also flexibility

Though we’re currently on PHP 7.0, the initial purpose of PHP was simply to serve as a connector between HTTP requests and a server database. Considering how capable a database can be, this simple layer of basic functions and a couple of variables is often all that you needed. In fact, for a lot of use cases, all you need is that thin layer of PHP, and that’s it.

JavaScript, however, gives you more flexibility and the opportunity to pull in libraries by means of jQuery. It’s so powerful that you can shift functions around as if they were objects. Besides, Node.js is a modern language and despite some frustrating aspects also offer some really useful features, including the much-loved closures. So still PHP vs Node.js, but let’s keep going.

PHP vs Node.js: Growing code or multiple languages?

PHP code is expanding, but Node.js opens the doors to many languages. Many PHP developers have yearned to be able to do more with PHP than simply pull content from a database and present it in a tidy way. In a way their wish has been granted: you can now use HHVM (open-source virtual machine) to do much more than you could before, including the use of annotations and lambda expressions. Even if you are restricted to using HHVM for your code this is not so much of a problem as HHVM is actually very fast.

But why restrict yourself to HHVM when Node.js gives you what is literally dozens of options. With Node.js you can cross-compile so many languages that it really opens a world of opportunities. Whether you prefer C#, Lisp or other languages that could even include BASIC or, if you must, Pascal – there’s no arguing, you have choices. The fact that so many languages can be cross-compiled to run in Javascript is a huge advantage in many situations.

Client-side code using Node.js


It’s true that some websites don’t need to execute any code on the client side. They simply use PHP to generate HTML from a database and get done with it. This is especially important when pages are rendered by mobile phones with small brains. Because you don’t want a code-heavy client side that gets bogged down with a slow mobile processor. Besides, simple HTML is less likely to lead to glitches.


Yet there are advantages to keeping some of the workload on the client side. And Node.js is simply more efficient, especially in terms of server usage. You send less data over the internet because there is less HTML mark-up. And you don’t need to submit a huge chunk of HTML code every time a little bit of data changes. AJAX takes care of all of this. This way of coding is ultimately  useful if your website is very data-driven, and requires more interaction from the user.

Database Queries: Advantages for both PHP and Node.js

If you’re familiar with and love SQL, PHP could be the best option for you. PHP was built closely to MySQL and databases similar to it such as Percona or Drizzle. Besides, you can easily connect to other SQL database from Oracle or even MS. Simply by making some basic changes to the code you use. Because SQL and the SQL code is so universal, it makes it really easy to work with databases and PHP.

JSON is not a bad alternative, however, as this too has a wide spread of databases it is compatible with. If you’re thinking of non-SQL databases for your application JSON can turn out to be quite a good solution. Though you can match JSON with PHP too, the similarity between JSON and JavaScript makes it great in a JavaScript environment.

It’s all about speed – but which?

Often there is a trade-off between the speed of writing the code, and the speed of an application executing. This is definitely the case with PHP and Node.js, with PHP being incredibly quick to put together. With PHP you don’t need a compiler or any JAR files. And PHP is an excellent choice if you need a working project really quickly.

On the flipside, PHP code doesn’t execute that quickly. In contrast, Node.js is code that executes smoothly and quickly reducing the load requirement on your server. You also get access to callbacks, which wastes less time when you try to deal with multiple different threads. You’ll spend more time coding and compiling with Node.js. But your code will be more optimized in the end.

PHP and Node.js Ecosystems

Finally, one distinction between Node.js and PHP that is worth keeping in mind is this: Node.js has a single code base. While there was a split in Node.js a while back, the group behind it has, for the most part, stuck to its guns and provided developers with the consistency they need.

However, the ongoing activity around PHP has benefits. Competing spur frameworks and libraries of the different teams want to add more useful features and improve performance. Zend and HHVM are both excellent projects. But there is a risk that, in the long-run, you’ll end up developing code on a code base that is relegated to the ash heap.

PHP and NodeJS – Supported Technologies

Content Management Systems Apostrophe2, PencilBlue, Enduro.Js, Ghost WordPress, Opencart, Drupal, Magento, Joomla, ModX
Model-View-Controller frameworks Express JS, Sails JS, Koa JS Zend, Laravel, CodeIgniter, CakePhp, Symfony
HTML templates Mustache, EJS, Jade, Embedded JS Smarty, Twig, Blade, Volt
QA Jasmine, Protractor, Casper JS, Phantom.JS PHPUnit, Dusk, Codeception, Selenium
Caching Redis, Node-Cache Memcache, Redis
Rest API Restify, Loopback RestClient, Guzzle
Horizontal Scaling Amazon Elastic Beanstalk Varnish, Amazon Elastic Beanstalk
Profiling Internal profiler XDebug, Blackfire, XHProf

What’s great for both Node.js and PHP?

Plesk Onyx Hosting Platform

We realize that there are advantages to both languages. So we offer you the ability to host code in both PHP and Node.js, with hosting features tailored to each. Let’s have a look.


Node.js has really gained enormous popularity within a short period of time, and with good reason. JavaScript itself is so widely-used and well-understood, making it an excellent way to start building a new code base. Node.js is a great way to build lightning-fast web applications. We can help you run Node.js applications easily and with high speed, offering the following hosting capabilities:

  • You can add Node.js to an application by just a click or two.
  • Plesk lets you easily manage your live Node.js applications, including starting and stopping (or restarting) and also editing config files and installing NPM packages. Our Onyx hosting platform really offers it all.
  • Plesk Onyx for Linux also allows you to install different live versions of Node.js in the same instance, for additional flexibility.

Find out more about how Node.js works on Plesk Onyx


Plesk has always offered support for PHP. This reliable language has been around for a very long time and is the basic building block for millions of web applications. We offer a top PHP hosting solution, including the following features.

  • Onyx supports multiple PHP versions out of the box, just pick your preferred PHP version when you install.
  • Standard PHP handlers are automatically configured for you.
  • Alternatively, pick your choice of PHP version and handler, making available to your customers only the versions you choose.

Plesk Multiple Server Management – How it Works

The biggest challenges we run into as system admins and web experts are multiple server managementsite management, and maintenance. If we don’t do this right, we face consequences. We waste time and resources. So it’s essential to own a web hosting control panel – making the whole thing simpler. While being able to create sites, apps, automate tasks, handle website security, and more.

Plesk Onyx is an all-around control panel and WebOps solution. Devs rely on it for its coding environment. Not to mention everyday tasks as it offers many extensions. Including Node.js, Ruby, WordPress Toolkit, Joomla Toolkit and more.

Plesk Control Panel Bonuses

Plesk supports Docker, which empowers developers to create and manage their new software. Do this by managing and deploying all Docker containers straight from the control panel. Additionally, Plesk offers GitHub integrations – deploying apps and sites quick from a Git repository, remote or local.

Plesk server management continues to add to its multiple server management capabilities. By giving absolute control of multiple accounts and subscriptions across all servers.

Multiple Server Management with One Control Panel

Plesk’s Multi Server extension lets you administrate multiple servers and routine tasks with just one control panel. Doesn’t matter if you’re a hosting provider, reseller, or manage your own hosting. Constantly switching between several hostnames, username IDs, and so on is exhausting.

Plesk designed its Multi Server extension with this in mind. For effective and secure multiple server management. With this extension, you can perform hosting actions on many servers. And manage the infrastructure with ease. This because memorizing hostnames, passwords, and login identifications become unnecessary.

It’s similar to simple web server management. However, the same scope of features is related to a number of servers. All through a single control panel.

Use Plesk WordPress Edition

Why the Multiple Server Management Extension?

You can install this extension directly from Plesk’s extension list. But note that you need to install Onyx on all your servers first. You’ll have all the features that Plesk has. But with this extension, you’ll gain additional functionalities:

  • Managing as many customer subscriptions and accounts as you want from your control panel.
  • Choosing between any billing systems you like, including yours.

It’s a very useful business-ready platform. Ideal for development studios and web designers who manage many different sites and clients.

What Plesk Multi-server management Consists of

  • At least two nodes which are all connected to each other using the SDK extension.
  • The basic two nodes include Service nodes and management nodes.
  • Plesk multi-server that will be installed on all extensions with all nodes.
  • All of the nodes that will have the same license key and configurations.

Subscriptions and Customer Account Management

So we said that this system comes with two nodes – service and management nodes. You use the service node to manage hosting. Because it has the power to host sites, system databases and emails. It also ensures quality load-balancing. This is important since it decides which node will provide hosting for the new subscription. Meanwhile, the multi-server extension has a separate API extending from Plesk’s API. Giving the power to add commands within the system.

The management node is a single Onyx server. Useful for both customers and administrators. And it servers a single point login spot. All new customer accounts go into this node too. But remember, this node has no tools for any hosting actions. So we use the management node to create accounts and the service node to manage their hosting.

Additionally, when a customer logs into the management node, they see and manage all subscriptions hosted through service nodes. You can see the following information on the subscription tab:

  • Status – a status sign that shows whether a subscription is successful or not.
  • A service node IP address that is provisioned for a certain subscription.

This is how Plesk server management can help you with web server management and multiple server management. You as an admin can rely on this comprehensive platform for its capabilities at all times.

UPDATE: Starting from Plesk Onyx 17.8 Multi Server feature is no longer available

Plesk 12.5 and Node.js

Plesk Node Js setup

During the last few years, Node.js has been steadily growing in popularity. On top of that, according to StackOverflow, JavaScript is today’s most popular programming language. If you are a Node.js developer, you may be curious whether it is possible to host Node.js apps on Plesk. The short answer is “yes, it’s possible”. In this article, I’ll explain how to set up the environment step by step using an Ubuntu 14.04 server with Plesk 12.5 for my demonstration. If you want, you can use other OSes or Plesk versions, but there can be the minor differences in commands and instructions.

Continue reading