I don\'t know why I\'m getting this error. Meteor-up is a brilliant. Whenever I run the deploy command it gets to a time and terminates. Could it be that a timeout has been set
There is no substitute for reading the documentation before you ask questions.
You should also update the mup package like it's suggesting.
There is a setting deployCheckWaitTime
which might be applicable, but it looks like it's failing in the upload. I'm not sure if it includes the upload time, but it would be worth increasing it to check.
Ten minutes is a long time to be only 41% through the upload, so your upload connection is slow - can you tether through your phone for better speed?
If that doesn't work, have a look to see if the disk is full on the target server, or if some other timeout is getting in the way (like your computer going to sleep)
I do not know if it is still relevant, but maybe my answer will help someone else dealing with the same problem.
The task "Prepare bundle" was introduced in the version 1.3.0 of Meteor Up (see release notes):
After the bundle is uploaded to each server, a new task is run called "Prepare bundle". It installs the Meteor npm dependencies, rebuilds native modules, and stores the result in a docker image. This has a few benefits:
- The time in meteor.deployCheckWaitTime no longer needs to include the time to install npm dependencies
- When installing dependencies fails, it does not continuously restart until meteor.deployCheckWaitTime expires, and running with --verbose shows the full logs from npm install
- Dependencies are only installed once during each deploy. This means that mup start, mup restart, and mup reconfig are all much faster.
From the version 1.3.1 this task can be disabled by adding the option app.docker.prepareBundle
in mup.js and setting it to false
. I dealt with the same error a few weeks ago and with this workaround I was able to deploy my application to DigitalOcean.