Hacker News Reader

Comment by estsauver | Hacker News Reader

The one thing I really want from Digital Ocean is a guide that carefully explains how to set up the "private network" piece of the equation.

The "orange box" that represents the private network in each of the examples is taken for granted, but for someone coming from an application development perspective that piece isn't trivial to make. EC2 Security groups make that sort of box incredibly easy to make, but DO doesn't have anything like that.

View on HN

The article on setting up and effectively using the private network for what you're describing is actually now in our pipeline. It will probably be live this or early next week :)

You can find our most recently published tutorials in our community here: https://www.digitalocean.com/community/?filter=tutorials or catch it in our twitter feed (@digitalocean)

Great! If that article would contain setting up custom hosts without using the HOSTS file (local DNS?), that'd be awesome. I don't like those ugly IP-addresses.

Awesome! Thank you very much!

Private Networking is available at certain data centers, like NYC2 == yes, vs. SFO1 == not yet.

But these apply to your desired documentation:

* https://www.digitalocean.com/company/blog/introducing-privat...

* https://digitalocean.com/community/articles/how-to-set-up-an...

This "private networking" is private to the every DO droplet in the same datacenter. If you expose a port for private networking in a data center and I get your IP I can access it if I also get a droplet in that data center.

As promised— here's the article that covers that info:

https://www.digitalocean.com/community/articles/how-to-isola...

Let us know in the comments if you have any other suggestions :)

Reply on news.ycombinator.com