Meteor 1.3 deploy Error with MUP

[benlavalley]

I found/fixed this a month ago and shared the resolution on github which involved tweaking mup to force --architecture os.linux.x86_64" – https://github.com/meteor/meteor/issues/6525#issuecomment-199088309). Wish I’d have seen this thread earlier to contribute.

I’m in the camp that still needs/prefers to use regular mup for deployment - glad to see I’m not alone

[redhead]

I had some issues with PhantomJS installation (bitbucket server returning 403) so I just disabled installing PhantomJS in mup.json.

I fixed this issue upgrading npm on the serve to npm install -g npm@2-latest still no luck with 1.3 on mup though.

[castlefields]

M4v3R Fork: https://github.com/M4v3R/meteor-up

Worked like a charm for me - Thanx!

[aadams]

@piyush

The issue was new meteor build system i guessmeteor build /path/to/build --architecture os.linux.x86_64

with the beta it was working because we still had Meteor 1.2 build tool and now thats changed i think few edit in mup code will solve it…

The output of this a tar, and we can uncompress, which gives us a bundle. We can’t point MUP to that bundle or tar, MUP will error out that we’re not in a Meteor project directory.

So how do we point MUP to the properly built Meteor build?

What lines of code within MUP@0.11.3 will fix this?