Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: ENOENT: no such file or directory, stat '/Users/jsantana/.meteor-now/build/projectname.tar.gz #89

Open
johhansantana opened this issue Dec 2, 2017 · 5 comments

Comments

@johhansantana
Copy link

Getting this error when trying to deploy a meteor app version 1.2.1

Error: ENOENT: no such file or directory, stat '/Users/jsantana/.meteor-now/build/projectname.tar.gz

meteor-now version: 0.5.2
node version: 8.7.0
npm version: 5.5.1

@lesliedoghouse
Copy link

Same here... Anyone have solution?

@purplecones
Copy link
Collaborator

Can you provide the entire console output that you see?

@Xananax
Copy link

Xananax commented Apr 20, 2018

Same here, getting:

✔ [METEOR-NOW] - Building meteor app (this can take several minutes) 
⚠ [METEOR-NOW] - WARNING: Did not pass a MONGO_URL. Bundling a NON-PRODUCTION version of MongoDB with your application. Read about the limitations here: https://git.io/vM72E 
⚠ [METEOR-NOW] - WARNING: It might take a few minutes for the app to connect to the bundled MongoDB instance after the deployment has completed. 
✔ [METEOR-NOW] - Preparing build 
✖ [METEOR-NOW] - Error: ENOENT: no such file or directory, stat '/home/xananax/.meteor-now/build/razor-project.tar.gz' 
⢀⠀ [METEOR-NOW] - Deploying build (this can take several minutes) args are  { _: [ '/usr/bin/node', '/usr/bin/meteor-now' ],
  help: false,
  version: false,
  public: true,
  '$0': '/usr/bin/meteor-now' }
✔ [METEOR-NOW] - Deploying build (this can take several minutes) 
✔ [METEOR-NOW] - App url is undefined 
Node#moveTo was deprecated. Use Container#append.

Running meteor-now --public -d gives me:

ℹ [METEOR-NOW] - clearing build folder 
ℹ [METEOR-NOW] - Building meteor app (this can take several minutes) 
ℹ [METEOR-NOW] - $ meteor build /home/xananax/.meteor-now/build --server-only --architecture=os.linux.x86_64
app/client/lib/semantic.less.css: warn: There are some @import rules those are not taking effect as they are required to be in the beginning of the file.
Node#moveTo was deprecated. Use Container#append.
ℹ [METEOR-NOW] - Preparing build 
⚠ [METEOR-NOW] - WARNING: Did not pass a MONGO_URL. Bundling a NON-PRODUCTION version of MongoDB with your application. Read about the limitations here: https://git.io/vM72E 
⚠ [METEOR-NOW] - WARNING: It might take a few minutes for the app to connect to the bundled MongoDB instance after the deployment has completed. 
ℹ [METEOR-NOW] - creating supervisord.conf 
ℹ [METEOR-NOW] - splitting bundle 
ℹ [METEOR-NOW] - Deploying build (this can take several minutes) 
args are  { _: [ '/usr/bin/node', '/usr/bin/meteor-now' ],
  help: false,
  version: false,
  public: true,
  d: true,
  '$0': '/usr/bin/meteor-now' }
ℹ [METEOR-NOW] - $ now /home/xananax/.meteor-now/build --name razor-project -e PORT=3000 -e ROOT_URL=http://localhost:3000 -e MONGO_URL=mongodb://127.0.0.1:27017 --public -d

Note that the same project, on the same machine, using the same versions of now, meteor, and mongo-now, uploaded fine previously

@remotealex
Copy link

I get the same issue when I'm not using the -d flag. I'm using webpack to bundle my app which must be triggering success before the tar.gz is actually available. I'm not sure why debug mode would make it work...

@solo999
Copy link

solo999 commented Oct 27, 2018

Same for meteor 1.8
meteor-now 0.7.0
node 8.11.4
npm 6.4.1

And it also doesn't have this issue with -d flag

meteor-now with Meteor 1.7 works ok with or without -d flag

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants