Google Cloud Platform - their PaaS or serverless solutions are extremely cheap. Also having 1TB free query on Bigquery is a true hidden gem in cloud. The same instance compared to other cloud vendors have better performance. We always needed fewer workers on GCP compared to AWS for example.
Ask HN: Where do you deploy to in 2018 and how?
31–40 of 85 posts
Re: Ask HN: Where do you deploy to in 2018 and how?
#32Google app engine
Re: Ask HN: Where do you deploy to in 2018 and how?
#33Most of my projects are Rails-based, and I tend to use DO [0], and have just discovered Hatchbox [1] to deploy. Super easy for side-projects to get started and deployed. Taken deploying side projects from days to minutes. [0] https://www.digitalocean.com/ [1] https://www.hatchbox.io/
I second DigitalOcean. Great UI, almost perfect API [0], excellent support.
[0] https://digitalocean.uservoice.com/forums/136585-digitalocea...
Re: Ask HN: Where do you deploy to in 2018 and how?
#34Dedicated servers colocated in town, via shell scripts, libvirt, and an in-house continuous integration service.
Re: Ask HN: Where do you deploy to in 2018 and how?
#35At present, we use a network of bare-metal servers, which are managed by Chef, with a custom deployment system which deploys build artefacts from CI as defined in Chef. It's tidy, smart and quick – but it does require a fair bit of infrastructure.
We're in the middle of piloting a switch to Nomad (https://www.hashicorp.com/products/nomad), replacing much of the custom deployment system with it, though still running on bare-metal servers. It's an absolutely fabulous bit of software that really hits the use-cases for an organisation of our size, so I'm excited to see how that works out.
For side-projects where things like HA aren't much of a concern, I've settled on some minimal shell scripts to deploy tarballs over SSH. It's actually pretty neat – CI builds a project, and runs a small script to copy the results to a server and restart the services. It's always worth considering the simple solutions if you don't need the more advanced features!
Re: Ask HN: Where do you deploy to in 2018 and how?
#36AWS, because we have to at work. Heroku for personal projects, because it's easy and fuss-free :-)
Re: Ask HN: Where do you deploy to in 2018 and how?
#37Using vultr.com for a few side projects. I'm planning to release an iOS app with a NodeJS and PostgreSQL backend. I find it to be somehow cheaper than DO but cannot say anything about the reliability.
Re: Ask HN: Where do you deploy to in 2018 and how?
#38If you like the git push flow of Heroku, i would recommend you to check out Hasura - https://hasura.io - Its a Baas + Paas for containers. Everything about your project is declarative and your apps are dockerized and deployed on to a Kubernetes cluster with free SSL.
Re: Ask HN: Where do you deploy to in 2018 and how?
#39As a sole developer, I have the luxury of keeping it simple - git push and if the tests pass, then ftp's to www.pythonanywhere.com
Re: Ask HN: Where do you deploy to in 2018 and how?
#40Dokku, running on an HP DM1 laptop in my cupboard. My ISP gives me a static IP and 100/100mb connection, so it’s quite good for my personal projects and some work tooling!