Hacker News Reader

Comment by natch | Hacker News Reader

Nice. For tutorials like this it would be nice to see more details on the "how" of each step. For example:

"We setup DNS info to point here (both NS1 and NS2..."

That's great, but it would be nice to see:

"Using the geodns web-based configuration tool, we setup DNS info to point here (both NS1 and NS2..."

"Running <insert full command line here including tool and all options used here> on <insert environment here>, we setup DNS info to point here (both NS1 and NS2..."

"By editing /etc/<file> on the <some environment>, we setup DNS info to point here (both NS1 and NS2..."

In other words specifics are always really great to include.

But still this was a really great writeup, not just for the overview it gives of one lightweight approach but for the comments it has kicked off.

View on HN

I think Genius and DigitalOcean = a match made in heaven. The quality would go from "the best" to "untouchable", if the comments were value adding. Imagine being able to dive deeper into any piece of the tutorial you wanted.

not to sound like a n00b, but what is Genius in your context?

I think he means Genius the company (formerly RapGenius) which annotates the web. (http://genius.com/)

oh ok thanks, I thought that, but I was also thinking maybe it was some tech stack like a docker container for a moment.

I was planning to publish a post with literally the same title as this one later this week (annoying coincidence as I guess mine will now be largely ignored - maybe I should wait a few weeks to let this space calm down, I'm not sure) with some in-depth step-by-step explanation - so watch out for that :)

How would I go about getting a link for the site you are going to publish article to?

This article title piqued my interest but in the end it lack some key pieces of info I would need to try.

It'll be on my blog, reinterpretcast.com and I'll probably tweet about it from @_joesavage. I'll probably also post to HN and Reddit, but I'm not sure if it'll gain much traction since it's so similar in concept to this article here.

It will, if its a detailed guide. This article, is an overview.

As expected (and possibly not aided by my timing, I'm unsure), my submission hasn't really gotten much attention - the link is here if you're interested though: http://www.reinterpretcast.com/roll-your-own-cdn

This comment is a model of quality feedback. It shows appreciation, not just shallow bookending, and gives detailed improvement examples. I know this is off topic a bit, sorry.

> Step 1: Order a DNS instance from Digital Ocean.

This also feels lacking to me. How does one order a DNS instance from DO? I can tell from the icon that it has something to do with CentOS but I don't see any sort of DNS server under their available applications or images for a one-click install.

great points. happy to take this approach on future posts and would love to collaborate in the future.

I really liked your write-up. As natch mentioned, it will be great to include more details in the article. I like the detail level of Digital Ocean articles.

It seems based on my recent trial experience with CloudFlare that both CDN startups might have this issue of incomplete/insufficient instructions and information for their users/customers to properly implement the solution and lot of assumptions about the skill level of users implementing the solution.

Actually, I landed up providing detailed instructions to CloudFlare on configuration and testing of their service. And a list of questions, answers to which should be readily available if CF is targeting enterprise customers.

thanks for the feedback. appreciate it.

Reply on news.ycombinator.com