[METEOR-NOW] - Something went wrong with now
AlABarazi opened this issue · 9 comments
I have :
meteor@1.4.2.1
- now@8.5.4
- meteor-now@0.5.3
in the command line :
meteor-now -e ROOT_URL=http://Awebsite.com
the result :
✔ [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 bund
led MongoDB instance after the deployment has completed.
✔ [METEOR-NOW] - Preparing build
✖ [METEOR-NOW] - Something went wrong with now
With mongdb:
meteor-now -e MONGO_URL=mongodb://:@ds163016.mlab.com:63016/lama-e ROOT_URL=https://mydomain.com -e NODE_ENV=production`
then I press enter nothing happen and I see >
I'm having the same issue. Is there a more detailed log file somewhere?
try adding the -d flag for debug. that should output a lot more information.
thanks @jkrup, I tried meteor-now -d but this is the only output I get:
ℹ [METEOR-NOW] - clearing build folder
ℹ [METEOR-NOW] - Building meteor app (this can take several minutes)
ℹ [METEOR-NOW] - $ meteor build /Users/damiaan/.meteor-now/build --server-only --architecture=os.linux.x86_64
ℹ [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)
✖ [METEOR-NOW] - Something went wrong with now
Are you experiencing the same problem or is this something that only me & @alabrazi are experiencing? (I get this error even with the sample application that is created with the meteor create helloworld command)
I needed to add a production.settings.json with {} at the root of my app because I had specified NODE_ENV=production (I don't use a settings.json file, but in this scenario, meteor-now expected there to be a production.settings.json.)
But this error also appears when deploying for development/testing and it doesn't go away if a add a settings.json file.
More detailed error logs would really help us out here, I think.
Thanks @TimHeckel, that was exactly my issue. Seems like something that could quite easily be flagged, I'd never have found it!
Same here tried specifying node dev environment along with development settings json, didn't work. Good old windows. Passing production didn't work either.