gistfile1.js

{
  // Server authentication info
  "servers": [
    {
      "host": "ip-1",
      "username": "root",
      "pem": "./bulletproofdo",
      "env": {
        "CLUSTER_BALANCER_URL": "https://one.bulletproofmeteor.com"
      }
    },
    {
      "host": "ip-2",
      "username": "root",
      "pem": "./bulletproofdo",
      "env": {
        "CLUSTER_BALANCER_URL": "https://two.bulletproofmeteor.com"
      }
    },
    {
      "host": "ip-3",
      "username": "root",
      "pem": "./bulletproofdo",
      "env": {
        "CLUSTER_BALANCER_URL": "https://three.bulletproofmeteor.com"
      }
    },
    {
      "host": "ip-4",
      "username": "root",
      "pem": "./bulletproofdo"
    }
  ],

  // Install MongoDB in the server, does not destroy local MongoDB on future setup
  "setupMongo": false,

  // WARNING: Node.js is required! Only skip if you already have Node.js installed on server.
  "setupNode": true,

  // WARNING: If nodeVersion omitted will setup 0.10.33 by default. Do not use v, only version number.
  "nodeVersion": "0.10.33",

  // Install PhantomJS in the server
  "setupPhantom": true,

  // Application name (No spaces)
  "appName": "meteor",

  // Location of app (local directory)
  "app": "../",

  // Configure environment
  "env": {
    "ROOT_URL": "https://bulletproofmeteor.com",
    "MONGO_URL": "mongodb://app:password@mongodb.com/dbname",
    "MONGO_OPLOG_URL": "mongodb://app:password@mongodb.com/local",
    "DISABLE_WEBSOCKETS": "1",

    "CLUSTER_DISCOVERY_URL": "mongodb://app:password@mongodb.com/dbname",
    "CLUSTER_SERVICE": "web"
  },

  // Meteor Up checks if the app comes online just after the deployment
  // before mup checks that, it will wait for no. of seconds configured below
  "deployCheckWaitTime": 15
}

why are you disabling websockets?

@westlakem: here is the quote from the main page: "We turn off WebSockets since cloudflare does not support SSL with WebSockets yet!"
https://github.com/meteorhacks/cluster

More details could be found here:
https://forums.meteor.com/t/effect-of-websockets-disabled/2918/2

I noticed that the current bulletproofmeteor site does use websockets and doesn't seem to use subdomains for balancing. Instead you get something like this:

{"websocket":true, "base_url":"https://bulletproofmeteor.com/cluster-ddp/20e8c2ce6338eaf67828307ce70f16447eb24fe7/web"}

Or:

{"websocket":true, "base_url":"https://bulletproofmeteor.com/cluster-ddp/fc2477d075ec18c2636b46d580eb30e4e22c7b23/web"}

What changed? We don't need to use subdomains as balancers? "https://bulletproofmeteor.com" can be used as a balancer itself?

@arunoda Just wanted to follow up on @elie222 observation. Are you relying on the multiple A records for "https://bulletproofmeteor.com" as the balancer?

@arunoda I have a rookie question. The fourth server that you take care of? And, should I configure nginx on each of the servers?