Actual settings for MUPX deployed self hosting VM example please


#1

Can MUPX deploy to Ubuntu self hosting instead of third party Digital Ocean etc? Just about every examples out there shows its usage with Digital Ocean, etc. But I don’t want to use any external providers, just an intranet wide for own company usage.


{
  // Server authentication info
  "servers": [
    {
      // "host": "IP Address", // Vagrant
       // "host": "172.17.0.2", // Docker
       "username": "root",
       "password": "password",
      // or pem file (ssh based authentication)
      // WARNING: Keys protected by a passphrase are not supported
      // "pem": "~/.ssh/id_rsa",
      // Also, for non-standard ssh port use this
      //"sshOptions": { "port" : 49154 },
      // server specific environment variables
      "env": {}
    }
  ],
  // Install MongoDB on the server. Does not destroy the local MongoDB on future setups
  "setupMongo": true,
  "setupNode": true,
  "nodeVersion": "0.10.40",
  "setupPhantom": false,
  // Application name (no spaces).
  "appName": "spark2acs",
  // Location of app (local directory). This can reference '~' as the users home directory.
  // i.e., "app": "~/Meteor/my-app",
  // This is the same as the line below.
   "app": "..",
  // Configure environment
  // ROOT_URL must be set to your correct domain (https or http)
  "env": {
    "PORT": 3000,
    "ROOT_URL": "http://localhost:3000",
    "CLUSTER_WORKERS_COUNT": "auto",
    "MONGO_URL": "mongodb://@localhost:27017/appName"
  },
  // Meteor Up checks if the app comes online just after the deployment.
  // Before mup checks that, it will wait for the number of seconds configured below.
  "deployCheckWaitTime": 600,
  //  "ssl": {
  //    "pem": "./ssl.pem"
  //  },

  // show a progress bar while uploading. 
  // Make it false when you deploy using a CI box.
  "enableUploadProgressBar": true
}

#2

Yes it can - are you having a specific problem when trying to use it?


#3

Hi Huge

So MUPX works with 1.3.2.4?

Seems like people are using this fork instead, or stay with original MUPX from Arunoda?

I just don’t know how to get IP address and all the other settings for a non-Digital Ocean(i.e self hosting) deploy because for Docker you will need IP address which is normally :

$ docker inspect --format ‘{{ .NetworkSettings.IPAddress }}’ eb714c103c40
172.17.0.2

But using this as “host”: “172.17.0.2” doesnt work as I cannot even ping to it?

Though for a Digital Ocean deploy it worked.


#4

I’m not sure about 1.3.2.4, but I know the newest version of mup (kadirahq/meteor-up) works with the latest version of Meteor.

With the latest version of mup the only IP you need to worry about is the IP used to connect to your server. See the Example File section of the mup docs.


#5

I thought MUPX was the only one supported since mup was not, but not kadirahq/meteor-up is the latest it seems, but the configuration looks daunting…


#6

kadirahq/meteor-up - it’s the mupx replacement, and is the only one that’s currently being supported.


#7

Just followed this to update node and npm since now it is asking ssh2 now

$ mup init
Error: Cannot find module ‘ssh2’

But after update still ssh2 error?

$ node --version
v4.5.0

$ npm --version
3.10.3


#8

YMMV but I was using the mupx branch with 1.3.4.1 for a pretty long time without much hassle. Although you will be stuck on the old node and mongodb.

There has been some active discussion about using a fork of mup with a docker image that runs the new node (allowing for 1.4 deployments with mup) but that isn’t something I’ve tackled personally.