HN user

andrewsomething

183 karma

API Engineering @ DigitalOcean

I'm andrewsomething many places on the internet including StackExchange and GitHub. Some places I'm known as simply asb like in Debian and on DigitalOcean.

[ my public key: https://keybase.io/andrewsomething; my proof: https://keybase.io/andrewsomething/sigs/AjYri8fzpiLhAYbawDajj-eloo9fQ24T2HHoMPLWEmA ]

Posts14
Comments39
View on HN

Hi! If you have never applied a promo code to your DigitalOcean account in the past, this code will still work for you. It's really just meant to give new users a chance to try out DO, and we've provided similar opportunities many times in the past.

Just to be clear, we are powering free CI runners for all GitLab.com users. In all honesty, the promo code was a bit of an afterthought.

Sorry to hear that. That does sound incredibly frustrating. Send me an email at asb@digitalocean.com We can discuss how DO can support your hackerspace, and I can take a deeper look into why you got caught up in our verification process.

Great response! I can totally understand the feeling.

We do work with a number of other incubators. DO itself is an alumni of TechStars. We have some stuff in the works with 500 Startups. We're definitely interested in working with other incubators as well. If you're involved with one, feel free to reach out to me at asb@digitalocean.com I'll make sure to get you to the right folks at DO.

If you're not in an incubator, check out the link I shared below. There's still a lot our customer success team can do for you.

Thanks!

Storage and networking are both areas we're investing a lot of work into right now. Blob storage isn't the first on the roadmap on the storage side, but I'll definitely pass on this feedback.

We have a lot of interesting stuff coming up later this year around networking. Some of it will be behind the scenes, but it is going to open up a lot of new possibilities for user-facing features. We're looking to give users a lot more control over their network while maintaining our focus on UX simplicity.

Might be a good time to mention we're hiring network engineers as well:

https://www.digitalocean.com/company/careers#software-engine...

Hi! I'd love to hear your feedback about our documentation. I work with the team that produces our tutorials. Are there areas you don't think we cover well, or is it something else? With 1,200+ tutorials, our docs are actually something I'm extremely proud of, but we're always looking to improve.

There seems to be a bit of confusion about how we handle kernels at DO. Hopefully I can clear things up a bit. On newer distro versions (e.g. Ubuntu >= 15.04, Debian 8, Fedora, CoreOS, FreeBSD) we no longer use "external" kernels. You are free to compile and use custom kernels. We're happy with what we've seen, and with Ubuntu 16.04 around the corner our default distribution will have support for this as well. After that point, we'll be backporting the change to older releases.

For Droplets still running with external kernels, we import new ones on a regular basis as they are released. If you happen to need one that hasn't been imported yet, just open a support ticket and the team will do so.

Depending on demand, adding other BSD variants is certainly a possibility. We had to start somewhere, and the FreeBSD community has been very vocal about wanting to see this happen. This is the first non-Linux OS we've decided to support, so we're excited to get feedback on it.

We built the DO community site from scratch as there was nothing else out there that offered the tight integration we wanted between presenting content and offering a place to ask questions and discuss. Even though it didn't meet all of our requirements, we're big fans of Discourse. It's a great platform for hosting discussions.

If you're looking for something that follows the Q&A model, there are quite a few StackOverflow inspired sites out there:

http://meta.stackexchange.com/questions/2267/stack-exchange-...

Right. When Sergey Belove originally reported this to DigitalOcean, one of our engineers reported and fixed this in upstream Doorkeeper.