CEO of https://zeit.co here! Happy to answer any questions throughout the day :)
Nice, is it meant for permanent hosting or just for prototyping and how does it compare to Cloudnode (https://cloudno.de)
Now: realtime Node.js deployments
51–60 of 121 posts
Re: Now: realtime Node.js deployments
#52Re: Now: realtime Node.js deployments
#53Red 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? https://www.openshift.com/
Our focus is on empowering the realtime JavaScript cloud with its rich module ecosystem. With the advent of microservices, code will become more succinct. Your backends will be aggregations of small functions with clear inputs and outputs. The syntactic differences between languages will matter less. Our bet is that JS has the largest and most prolific community!
> Our focus is on empowering the realtime JavaScript cloud with its rich module ecosystem.
I'm sorry, but that's just meaningless buzzword bingo.
Re: Now: realtime Node.js deployments
#54Earlier quoted context omitted.
Our biggest focus is `npm install` performance. We have multiple caches to make it the best possible experience for you. Every time you run `now` it's as if you had installed from scratch (including semver invalidations like ^ or ~). The focus is on reproducibility.
> Every time you run `now` it's as if you had installed from scratch (including semver invalidations like ^ or ~). The focus is on reproducibility. This is very confusing to me as these seem to be contradictory statements. Installing "from scratch" (I take this to mean, as if node_modules is an empty folder) is not a reproducible action, as all it takes is one sub-dependency releasing a new version to change your ins…
I think it's "reproducible" in the sense that it starts from scratch every time, rather than sometimes starting from scratch, and other times starting with a pre-populated node_modules. If you want actual versioning reproducibility, you'll need to put an npm-shrinkwrap.json in your root.
Re: Now: realtime Node.js deployments
#55Earlier quoted context omitted.
Our focus is on empowering the realtime JavaScript cloud with its rich module ecosystem. With the advent of microservices, code will become more succinct. Your backends will be aggregations of small functions with clear inputs and outputs. The syntactic differences between languages will matter less. Our bet is that JS has the largest and most prolific community!
> Our focus is on empowering the realtime JavaScript cloud with its rich module ecosystem. I'm sorry, but that's just meaningless buzzword bingo.
translation: they use websockets on AWS with insane numbers NPM modules.
Re: Now: realtime Node.js deployments
#56Very 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.
it's easy on heroku. I haven't done it with native modules though
Re: Now: realtime Node.js deployments
#57Earlier quoted context omitted.
Our focus is on empowering the realtime JavaScript cloud with its rich module ecosystem. With the advent of microservices, code will become more succinct. Your backends will be aggregations of small functions with clear inputs and outputs. The syntactic differences between languages will matter less. Our bet is that JS has the largest and most prolific community!
> Our focus is on empowering the realtime JavaScript cloud with its rich module ecosystem. I'm sorry, but that's just meaningless buzzword bingo.
Actually, I think the issue is that you just don't understand the meaning of those words.
The "rich module ecosystem" he is speaking of refers to npm. With node and npm it is trivial to install a few modules from the command line, write up a custom server, and very quickly have yourself a dynamic web page or API.
The "realtime JavaScript cloud" is basically any node application running on a service like Heroku or with any number of hosts and providers ranging from self-managed VPNs to esoteric AWS services. Applications that run on this realtime JavaScript cloud are incredibly portable as engines can be fired up and torn down very quickly across both server-side and client-side environments.
This service that he has been a part of creating does exactly this. It empowers the user by streamlining existing development processes.
I would say that his sentence is rather meaningful contemporary industry jargon.
Re: Now: realtime Node.js deployments
#58Earlier quoted context omitted.
Really cool website! I'm confused though exactly what is going on. Is this kind of like Heroku? What are the pros and cons of this service? For context, I'm currently running a production node/express/mongo service on Digital Ocean.
Compared to other providers, there's absolutely no setup involved. No Procfiles, ports, containers, dynos, processes, instances… Just type `now` where you have a `package.json`.
How is there no port? I have to run my server on some port, are you saying I can choose whatever my port I want and your service detects that somehow? I don't need to use process.env.PORT ?
Re: Now: realtime Node.js deployments
#59CEO of https://zeit.co here! Happy to answer any questions throughout the day :)
Can this be used with a CI service very easily?
Re: Now: realtime Node.js deployments
#60What 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?