Where to deploy #8
Description
As stated in TODO:
Figure out infrastructure (where to deploy, scaling, user auth, etc)
I've been impressed with ZEIT's Now and have been using it for my deployments.
You literally just type now in your application's directory and it creates an immutable deploy that you get a unique link for. Then you can alias that deploy to your domain name with another command, now alias. All the config is in your package.json or now.json.
now allows you to take your JavaScript (Node.js) or Docker powered websites, applications and services to the cloud with ease, speed and reliability. In practical terms, any directory that contains a package.json or Dockerfile can be transported to the cloud with one command: now.
I like this part too:
We don't depend on a single specific cloud provider, but abstract them instead. This means that we can always find the best combination of cost, performance, reliability and resistance to failure or censorship.
They have user auth coming. But be careful with auth since users who are getting alerts from certain servers may be targeted. ZEIT employees are active on slack so maybe could ask them there how exposed this traffic is and if they have a solution such as rotating servers. Everything is by default encrypted over HTTP/2, so this may be moot, but better safe than sorry.