←back to thread

DigitalOcean App Platform

(pages.news.digitalocean.com)
646 points digianarchist | 1 comments | | HN request time: 0s | source
Show context
user5994461 ◴[] No.24700185[source]
I am so glad to see this. I was looking to deploy an app and the choice is either Heroku or manage your own server which I don't want to do.

Heroku gives instant deployment for the most common types of apps (python/java/ruby). It's PaaS done right, it's fantastic. You should really have a look if you're not aware of it, it's only $7 for a starter app.

Problem is, scaling up is about $50 per gigabyte of memory which makes it a dead end for anything non trivial. You're forced to go to digital ocean / Linode / OVH instead to have something affordable.

That leaves Digital Ocean as the only alternative (don't trust Linode) and it sucks because it only gives me a server to manage. I don't want to manage a server I want to run a (python) application. It's 2020 this sort of things should auto deploy from GitHub without bothering me to manage an operating system.

replies(19): >>24700693 #>>24700794 #>>24701039 #>>24702228 #>>24702633 #>>24702880 #>>24703398 #>>24703543 #>>24703620 #>>24704410 #>>24704873 #>>24705031 #>>24705668 #>>24706188 #>>24706382 #>>24707003 #>>24709134 #>>24716137 #>>24727185 #
sneak ◴[] No.24707003[source]
You shouldn’t trust Digital Ocean, either. They’ve a history of being shady liars about platform security.

https://github.com/fog/fog/issues/2525

https://news.ycombinator.com/item?id=6983097

replies(1): >>24718212 #
names_are_hard ◴[] No.24718212[source]
I read that thread, it's quite concerning. Now I'm wondering how to determine if other providers are doing the same thing. I suppose I can test on a new instance, but that can only tell me definitively if they are doing it, not if they're not.
replies(1): >>24744921 #
1. sneak ◴[] No.24744921[source]
The thread is 7 years old, and DO hired competent people along the way.

The issue is not that it happened, or that they had clueless staff; the issue is that their board and senior management thought that the best way to respond to their own error was to blatantly lie in their blog that there was no problem at all.

It seems to have worked; they're massively valuable now.