DigitalOcean
Ask HN: Where do you deploy to in 2018 and how?
71–80 of 85 posts
Re: Ask HN: Where do you deploy to in 2018 and how?
#72I do things in an old-school way. 2 Bare metal servers at different data centers with totaluptime.com acting as a load balancer with auto-failover. Deployment is done via SFTP by pressing the publish button in Visual Studio. This will deploy to the inactive server. I then manually trigger tests on GhostInspector (this could be automated via API) to make sure I didn't break anything. Then I run a custom script to make…
This is probably a very dumb question, but what exactly do you mean when you say you run bare metal servers at a data center? I run a kind of similar setup sans Visual Studio, so I'm very interested in understanding your setup a little better.
Bare metal means I'm not running on VMs, but on dedicated servers, like the ones you can find on OVH and many others.
Re: Ask HN: Where do you deploy to in 2018 and how?
#73I do things in an old-school way. 2 Bare metal servers at different data centers with totaluptime.com acting as a load balancer with auto-failover. Deployment is done via SFTP by pressing the publish button in Visual Studio. This will deploy to the inactive server. I then manually trigger tests on GhostInspector (this could be automated via API) to make sure I didn't break anything. Then I run a custom script to make…
Thanks for sharing, I'm considering bare metal as well for a project. Is latency between the two data centers an issue for you, e.g. is one of your two servers running a SQL database as master?
Right, I replicate the database. Latency hasn't been a problem for our volume. During our peak hours we get 30 requests/second, so it's pretty manageable.
Re: Ask HN: Where do you deploy to in 2018 and how?
#74I'm surprised how many people here are snow-flaking their own web application servers instead of just using Heroku. Heroku is $25/dyno/month. At $100/hr for a dev a Heroku dyno costs 15minutes of dev time per month. If you spend just a day tinkering with your application server VMs or updating docker images running your Rails app every month — you could have bought 32 Heroku dynos instead.
Well you usually need at least two-three dynos plus a database. This takes the price to $100-$125 / mo which is still a good savings over hiring a sysadmin.
But some services provide a good subset of heroku functionality on your own servers for a flat fee which is where I think the sweet spot is now.
Re: Ask HN: Where do you deploy to in 2018 and how?
#75I can recommend APPUiO [0] which is a Swiss based container platform running OpenShift [1] and providing a full PaaS experience. The crew is reachable under [2], answering any questions in the chat. Disclaimer: I work for VSHN, the company behind APPUiO.
[0] https://appuio.ch/en/public.html [1] https://www.openshift.org/ [2] https://community.appuio.ch/
Re: Ask HN: Where do you deploy to in 2018 and how?
#76Work: AWS.
Personal projects: Github pages (mostly react apps, e.g. [1, 2]), GAE (python backends, e.g. [1]), Google Spreadsheet (data backend, e.g. [2]), Firebase (e.g., [3]).
Re: Ask HN: Where do you deploy to in 2018 and how?
#77Google 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.
I also prefer GCP over AWS. GCP has better documentation, better UI and UX, better console and just overall more friendly.
Re: Ask HN: Where do you deploy to in 2018 and how?
#78I do things in an old-school way. 2 Bare metal servers at different data centers with totaluptime.com acting as a load balancer with auto-failover. Deployment is done via SFTP by pressing the publish button in Visual Studio. This will deploy to the inactive server. I then manually trigger tests on GhostInspector (this could be automated via API) to make sure I didn't break anything. Then I run a custom script to make…
As someone who like down-to-earth first approach, I find it strange that reading about doing old-school way sounds, actually, refreshing. It would be interesting for anybody who builds starting from small blocks, do you have some blog about ongoing stuff?
Re: Ask HN: Where do you deploy to in 2018 and how?
#79I use DO Droplets (5$ - 10$) to host multiple static websites with server blocks or multiple applications (Node.js) with Dokku. So far, it has worked out for me very well. If you are interested in Dokko, you can find a guide for my setup over here [0].
- [0] https://www.robinwieruch.de/deploy-applications-digital-ocea...
Re: Ask HN: Where do you deploy to in 2018 and how?
#80Kubernetes, both in-house and on AWS. I couldn't live without it anymore, it's just so nice to use and easy once you've gotten over the initial learning curve. kubectl apply -f for simple deployments, Helm for more complex ones.
What services on AWS do you use with Kubernetes? Any good resources re: Kube and AWS?