I used to use a project called now on npm that was abandoned a few years ago (<a href="https://github.com/Flotype/now" rel="nofollow">https://github.com/Flotype/now</a>). I was curious how this new project was using the same name on npm as the previous now that I had used.<p>Looking at the npm release history, versions <= 0.8.1 are the old project, and the new project picked up at 0.9.0 (should have been 1.0.0 I guess). This is consistent with npm's statements about package name transfers during the leftpad debacle, but there's just something weird about reusing package names for totally different projects...
Had to read three pages and still haven't quite confirmed that this is node.js hosting. But based on the pricing page, I guess it is. Can you please just say that? Just say "It's node hosting and the deployment system is fast." You literally just stole some of my life.
Red Hat Openshift has a solid free tier, free SSL, git push deployments, node / ruby / python / java / php / etc., mysql / postgres, redis. Why would I use this over that?<p><a href="https://www.openshift.com/" rel="nofollow">https://www.openshift.com/</a>
The pricing structure is missing a couple of middle tiers and overall the service lacks useful features. For instance: I could buy a $5/mo droplet in Digital Ocean, one click install node, even use my own domain and manage deployments/restarts almost as easy. For that money I get 1TB transfer and 20GB ssd and many more features (b/c I basically get a VPS where I can do whatever). It takes me 10 min to setup the server and zero minutes to deploy each new version (I use deploybot so every git push is really a deployment).<p>Some things are not clear:<p>"Dynamic realtime scaling" Forever? Unlimited? Say 1MM concurrent API calls for $15/mo?<p>URLs change after each deployment? Do I need to update endpoints on all clients?
Off topic: Right when I saw the terminal, I instinctively typed "ls". Not sure now if that's what triggered the animation or not but regardless it was a neat occurrence (I also just want to leave it at that ;) ) Yayy muscle memory!
> NOTE: npm start has to listen on a port. It can be any port!<p>Does this mean you forward port 80/443 to whatever port the app is listening on, or I can have my app listen on random external ports?
What makes the deployment "realtime"? Is it just that you get terminal output of the deploy happening? That's been around for a while now. Or am I missing something?
This looks very promising for the node community. I was wondering which cloud infrastructure service they went with to power this. According to the FAQ, they don't rely on just one. Very cool, and if implemented correctly, more resilient.<p><pre><code> Multi-cloud.
We don't depend on a single specific cloud provider, but abstract them instead.
</code></pre>
P.S. Is the markdown parsing broken on the FAQ? Or is that part of the look they're going for?
Does this support native modules and is it running on Linux 64?<p>If so it'd be an interesting "hack" to have it run arbitrary code. You could have the default "npm run" script download a python/ruby/golang/foobar runtime and kick start an app on the expected port.
Very cool! I was just saying how hard it is to get someone to deploy a quick node app. Trying it with a React + Express app right now. Taking a while to deploy but I assume you are getting hammered.
You don't really mention this in the pricing section but I assume for the paid plan, it gives you the option to hide the /_src feature based on something (IP, etc.)?
Looks neat for demo apps. I did try it out on one of my simpler express based apps and it failed during the npm install. Looks like this is possibly using ied?
Seems cool.
After many years on node, and even writing a deployment service once (paastor) - just plain VPS, nar to make an executable, then scp onto an Ubuntu server, and scp a logrotate and upstart conf - that's all you need man.
Fantastic intro write up to read in a mobile browser. Wish many products get to what matters like these in their descriptions. Interesting enough to try immediately!