meteor-up: mup setup doesn't do anything

Hi,

I migrated to Meteor 1.3 and now mupX is not working anymore. Some posts forwarded me to kadirahq’s mup version so I am trying that now. I follwed the npm intall and link and installed mup. I have setup my mup.js file as follows:

'use strict';

module.exports = {
  servers: {
    one: {
      host: '{host ip}',
      username: 'ubuntu',
      pem: '~/.ssh/prospa'
    }
  },

  meteor: {
     name: 'app',
     path: '~/www/prospa/app,
     servers: {
       one: {} //list of servers to deploy, from the 'servers' list
     },
     env: {
       ROOT_URL: 'http://thedomain.com',
       MONGO_URL: 'mongodb://localhost/27017'
     },
     dockerImage: 'madushan1000/meteord-test', //optional
     deployCheckWaitTime: 60 //default 10
   },

  mongo: { //optional
    oplog: true,
    port: 27017,
    servers: {
      one: {},
    },
  },
};

When I run mup setup nothing happens. Just a 0.5 second lag and another shell line shows up. When I remove the mup.js I get an error telling me the mup.js is missing. So it is doing something.

What am I doing wrong?

Also, will this config setup a mongo in a docker image like mupx? We will move to a separate mongoDB soon so I will use the mongo_url for that.

I am a bit stressed because we are going live in 4 weeks and since the Meteor 1.3 upgrade a lot of stuff is broken/had to be fixed and now the deployment is down too.

Help would be very much appreciated.

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 17 (5 by maintainers)

Most upvoted comments

After some digging I found that the PEM can’t start with ~/.shh/pemfile but it has to be `/Users/{name}/.ssh/pemfile. (on osX). I didn’t get any error message on this. Maybe add some error message if _fs2.default.readFileSync is not retrieving the pem file? This was the file mup-api.js, function _loadSessions.

+13

mattiLeBlanc on Apr 1, 2016

I beat my head upon the wall for hours, nay, days, upon end, never imagining that support for a home-directory tilde was something that even COULD change in an npm module.

WHY ON EARTH IS THIS INFO NOT ON THE FRONT PAGE OF THE GITHUB REPO???

silent failure is not the right way… when i commented the pem line out, i get an obvious error. this failure was not cool… especially as our entire software framework community seems to be dependent upon this particular script. (node bundling etc being what it is…)

vectorselector on Aug 4, 2016

I got the same problem at first. But I solved then. That README makes people confuse. for example: You have a project called meteor_test

cd meteor_test

then current dir is:

>meteor_test

then mkdir .deploy

>meteor_test/.deploy

then cd .deploy and run mup init

>meteor_test/.deploy
                                  \_mup.js
                                  \_settings.json

at last run mup setup like this:

>meteor_test/.deploy > mup setup

You are under the .deploy dir to run mup setup and mup deploy . This is important… Then there will be some things appeared…

llqgit on Jun 29, 2016