[gkoberger]

Just to piggyback for people confused:

It's zero-configuration Node hosting, for permanent lightweight microservices or temporary Node projects that need to be accessible online.

In other words, it's as close to uploading PHP files to a server that you'll get with Node.

For people wondering, the creator is Guillermo Rauch, who is behind Socket.io and LearnBoost (the company that brought us Express, Mongoose, Stylus, Jade, etc... basically the entire Node stack)

[mmaunder]

Why not just upload node files to a server?

[gkoberger]

For PHP, you upload index.php, go to yoursite.com/index.php, and it works. Node isn't like that at all. For example, here's the "Hello World" guide for getting Node started:

https://www.digitalocean.com/community/tutorials/how-to-set-...

This is basically the problem `now` is solving... "what if Node was as easy as PHP?"

[smt88]

> For PHP, you upload index.php

That's not inherent to PHP. It's just how most hosts are set up. The only major difference is the order in which things are done (and the necessity to have shell access to the host.)

The real comparison is this:

# PHP # 1. Install a server 2. (Possibly optional) Install a process manager 3. (Possibly optional) Configure the process manager 4. Configure the server 5. Start the server 6. Upload files

# Node # 1. Install Node 2. Upload files 3. Start the server

[goldbrick]

So you have 3 configuration steps for PHP and none for Node? You're completely full of it.

[smt88]

6 for PHP, 3 for node. There's an objective difference: node has a built-in, production-ready server.

[goldbrick]

Silliness. Here's me building a production php server:

1) `apt-get install php5 apache2`

2) upload index.php

3) There is no step 3

[l0gicpath]

I suppose you could do that, but I reckon their main selling point is convenience. Same argument can be made for any cloud hosting service.

Why not just buy a VPS and set it up yourself, it's just more convenient for some people.