raykao

Digital Ocean recently released private networking support in their NYC2 Data center.

They also published a blog post on how to setup a new droplet with private networking. But one thing the post doesn't do is tell you how to scale your private network for many boxes. One approach is obviously to edit /etc/hosts (but this gets annoying when you add a new box). A better way is to create an internal DNS zone (via the digital ocean web interface) and have your droplets use it:

Steps

setup the internal DNS zone file

1. Login to digital ocean
2. Click "DNS" on the right hand menu

plentz

# to generate your dhparam.pem file, run in the terminal
openssl dhparam -out /etc/nginx/ssl/dhparam.pem 2048

krames

require 'fog'

# Please replace these with the approprate values
RACKSPACE_USERNAME = "YOUR USERNAME"
RACKSPACE_API_KEY = "YOUR API KEY"
RACKSPACE_TEMP_URL_KEY = "#192!29jd!23990192DSAF"

puts "Creating Storage Service"

begin

alexjs

#
# Slightly tighter CORS config for nginx
#
# A modification of https://gist.github.com/1064640/ to include a white-list of URLs
#
# Despite the W3C guidance suggesting that a list of origins can be passed as part of
# Access-Control-Allow-Origin headers, several browsers (well, at least Firefox) 
# don't seem to play nicely with this.
#

jgwhite

var App = Em.Application.create();

App.ApplicationController = Em.Controller.extend();
App.ApplicationView = Em.View.extend({ templateName: 'application' });

App.HomeController = Em.Controller.extend();
App.HomeView = Em.View.extend({ templateName: 'home' });

App.AuthController = Em.Controller.extend({

michiel

#
# Wide-open CORS config for nginx
#
location / {

     if ($request_method = 'OPTIONS') {

        add_header 'Access-Control-Allow-Origin' '*';
        
        #