Comments (14)
It also happened to me.
What I know is that this happens when you install your project dependencies with npm install
instead of meteor npm install
.
So it makes me think that the real problem occurs when the dependencies are installed with a node/npm version different from the one used internally by Meteor.
We should try putting the "engines" property on package.json
equals to the node/npm version meteor is using in order to see if it solves the problem.
Something like:
"engines": {
"npm": "4.5.0",
"node": "4.8.1"
}
I am aware that now
service uses always latest versions of node/npm.
Let me know if it solves the issue
from meteor-now.
@tomyo can you post the entire log you see when you deploy with -d
flag and your package.json
file?
from meteor-now.
Any update on this issue ? I cannot find a way to install bcrypt
on production...
from meteor-now.
Hi @vladejs, thanks for the suggestion.
I went under ~/.meteor/packages/meteor-tool/1.5.1/mt-os.osx.x86_64/dev_bundle/bin
to find the versions, and added to package.json:
"engines": {
"npm": "5.3.0",
"node": "4.8.4"
}
sadly, nothing changed.
What else can I try?
Thanks!
from meteor-now.
@tomyo is it failing to deploy too or just showing that Note
? Because it says it: will work correctly, it is known to be approximately three times slower than the native implementation
from meteor-now.
@jkrup .
It's not failing to deploy, but I feel like so, because not having bcrypt
properly installed incurs on great hits on performance.
Is this difficult to solve?
from meteor-now.
Deploys fine, but it keeps restarting, as required dependencies are not being installed, or loaded.
The app fails with the error:
/bundle/programs/server/node_modules/fibers/future.js:280
throw(ex);
^
Error: Module ursa must be installed
And I have it under "dependencies": {...}
from meteor-now.
Okay. It's definitely an issue and would be great to fix. But as far as I'm aware bcrypt will only be used when logging in / creating passwords / etc so probably won't be noticable performance impact.
I did some googling and it looks like the Dockerfile
we use may not be capable of building bcrypt. I'll try to update it as per these dependencies https://github.com/nodejs/node-gyp#installation
from meteor-now.
so probably won't be noticable performance impact
Let's make 100 concurrent users login at the same time
I'll
try toupdate it as per these dependencies https://github.com/nodejs/node-gyp#installation
That would be great
from meteor-now.
@jkrup, in case you missed my comment, seems like no dependencies at all are being installed, for me at least.
from meteor-now.
Anyone else with this problem? For me is very serious, with packages not being installed, meteor-now became unusable for me. Have this payed account in now waiting..
from meteor-now.
Sure, I just did a fresh deploy, this are the logs:
Note: you are using a pure-JavaScript implementation of bcrypt.
While this implementation will work correctly, it is known to be
approximately three times slower than the native implementation.
In order to use the native implementation instead, run
meteor npm install --save bcrypt
in the root directory of your application.
Kadira: completed instrumenting the app
10/03 10:45 AM (16s)
{ "line": "106", "file": "percolate_migrations.js", "message": "Migrations: Not migrating, control is locked.", "time": { "$date": 1507038328636 }, "level": "info" }
/bundle/programs/server/node_modules/fibers/future.js:280
throw(ex);
^
Error: Module ursa must be installed to use WSSecurityCertTBK
at new WSSecurityCertTBK (/bundle/programs/server/npm/node_modules/transbank/lib/security/WSSecurityCertTBK.js:42:11)
at new TBK (/bundle/programs/server/npm/node_modules/transbank/lib/tbk.js:20:21)
at imports/startup/server/server.coffee:65:12
at Function.time (/bundle/programs/server/profile.js:309:28)
at /bundle/programs/server/boot.js:347:13
at /bundle/programs/server/boot.js:388:5
at Function.run (/bundle/programs/server/profile.js:510:12)
at /bundle/programs/server/boot.js:386:11
Here's package.json:
{
"name": "appName",
"private": true,
"scripts": {
"start": "meteor run --settings=development.settings.json",
"deploy-production": "DEPLOY_HOSTNAME=galaxy.meteor.com meteor deploy www.feriaferio.cl --settings production.settings.json",
"deploy-beta": "DEPLOY_HOSTNAME=galaxy.meteor.com meteor deploy beta.feriaferio.cl --settings beta.settings.json"
},
"engines": {
"npm": "5.3.0",
"node": "4.8.4"
},
"dependencies": {
"aws-sdk": "^2.70.0",
"babel-runtime": "^6.18.0",
"bcrypt": "^0.8.7",
"body-parser": "^1.15.2",
"cheerio": "^0.22.0",
"core-js": "^2.5.0",
"meteor-node-stubs": "^0.2.11",
"soap": "^0.16.0",
"transbank": "^1.1.2",
"ursa": "^0.9.4",
"wnumb": "^1.0.4"
}
}
Here's the meteor-now deploy -d output:
[METEOR-NOW] - running command: meteor build .meteor/local/builds --server-only --architecture=os.linux.x86_64
WARNING: The output directory is under your source tree.
Your generated files may get interpreted as source code!
Consider building into a different directory instead
meteor build ../output
[METEOR-NOW] - creating Dockerfile
[METEOR-NOW] - splitting bundle
[METEOR-NOW] - looking for meteor settings file production.settings.json in root of project
[METEOR-NOW] - found settings file
[METEOR-NOW] - running command: cd .meteor/local/builds && now -e PORT=3000 -d -e NODE_ENV=production -e MONGO_URL="(...)" -e ROOT_URL=(...) -e METEOR_SETTINGS='(....)'
> Deploying ~/proyectos/feriaferio/app/.meteor/local/builds under tomyo
> [debug] Detected `deploymentType` = `docker`
> [debug] Detected `deploymentName` = ""app""
> [debug] locating files /home/tomyo/proyectos/feriaferio/app/.meteor/local/builds: 11.974ms
> [debug] Getting files: 14.862ms
> [debug] Computing hashes: 479.418ms
> [debug] /now/create: 3583.258ms
> Ready! https://app-gwtkkqtgwk.now.sh [4s]
> [debug] total files 122, 121 changed.
> [debug] Will upload 121 files in 13 steps of 10 uploads.
<uploaded>
> Synced 121 files (114.89MB) [29m]
> Initializing…
> [debug] closing agent
> Building
> ▲ docker build
Sending build context to Docker daemon 120.6 MBkB
> Step 1 : FROM node:boron
> ---> 8095ae5163c9
> Step 2 : ENV NPM_CONFIG_LOGLEVEL warn
> ---> Using cache
> ---> e13d9ab3f3b5
> Step 3 : LABEL name "app"
> ---> Running in 211645b8acd1
> ---> 84b29f0c8733
> Removing intermediate container 211645b8acd1
> Step 4 : COPY . .
> ---> 02d8d11845a8
> Removing intermediate container 1f3235aca06a
> Step 5 : RUN cat *sf-part* > bundle.tar.gz
> ---> Running in 9d4b89e06e9c
> ---> f41a4dbe0f46
> Removing intermediate container 9d4b89e06e9c
> Step 6 : RUN tar -xzf bundle.tar.gz
> ---> Running in 5fdc1b1923ec
> ---> de00f1e8f7ec
> Removing intermediate container 5fdc1b1923ec
> Step 7 : WORKDIR bundle/programs/server
> ---> Running in 580c2274bdad
> ---> 9bbdf02254b7
> Removing intermediate container 580c2274bdad
> Step 8 : RUN npm install
> ---> Running in e763df440f84
> > [email protected] install /bundle/programs/server/node_modules/fibers
> > node build.js || nodejs build.js
> `linux-x64-48` exists; testing
> Binary is fine; exiting
> npm WARN lifecycle [email protected]~install: cannot run in wd %s %s (wd=%s) [email protected] node npm-rebuild.js /bundle/programs/server
> [email protected] /bundle/programs/server
> +-- [email protected]
> +-- [email protected]
> +-- [email protected]
> +-- [email protected]
> +-- [email protected]
> +-- [email protected]
> +-- [email protected]
> +-- [email protected]
> +-- [email protected]
> +-- [email protected]
> +-- [email protected]
> +-- [email protected]
> +-- [email protected]
> +-- [email protected]
> +-- [email protected]
> | +-- [email protected]
> | +-- [email protected]
> | | +-- [email protected]
> | | +-- [email protected]
> | | | `-- [email protected]
> | | +-- [email protected]
> | | `-- [email protected]
> | +-- [email protected]
> | +-- [email protected]
> | | `-- [email protected]
> | | +-- [email protected]
> | | `-- [email protected]
> | +-- [email protected]
> | | `-- [email protected]
> | +-- [email protected]
> | | `-- [email protected]
> | +-- [email protected]
> | | +-- [email protected]
> | | | `-- [email protected]
> | | +-- [email protected]
> | | +-- [email protected]
> | | | +-- [email protected]
> | | | +-- [email protected]
> | | | +-- [email protected]
> | | | +-- [email protected]
> | | | | +-- [email protected]
> | | | | +-- [email protected]
> | | | | | `-- [email protected]
> | | | | `-- [email protected]
> | | | | `-- [email protected]
> | | | +-- [email protected]
> | | | | `-- [email protected]
> | | | `-- [email protected]
> | | `-- [email protected]
> | +-- [email protected]
> | | +-- [email protected]
> | | `-- [email protected]
> | +-- [email protected]
> | | +-- [email protected]
> | | +-- [email protected]
> | | +-- [email protected]
> | | +-- [email protected]
> | | | `-- [email protected]
> | | +-- [email protected]
> | | +-- [email protected]
> | | +-- [email protected]
> | | | `-- [email protected]
> | | +-- [email protected]
> | | | +-- [email protected]
> | | | | +-- [email protected]
> | | | | +-- [email protected]
> | | | | +-- [email protected]
> | | | | `-- [email protected]
> | | | | `-- [email protected]
> | | | `-- [email protected]
> | | +-- [email protected]
> | | | +-- [email protected]
> | | | +-- [email protected]
> | | | | `-- [email protected]
> | | | +-- [email protected]
> | | | `-- [email protected]
> | | +-- [email protected]
> | | | +-- [email protected]
> | | | +-- [email protected]
> | | | | +-- [email protected]
> | | | | +-- [email protected]
> | | | | `-- [email protected]
> | | | `-- [email protected]
> | | | +-- [email protected]
> | | | +-- [email protected]
> | | | +-- [email protected]
> | | | +-- [email protected]
> | | | +-- [email protected]
> | | | +-- [email protected]
> | | | `-- [email protected]
> | | +-- [email protected]
> | | +-- [email protected]
> | | +-- [email protected]
> | | +-- [email protected]
> | | | `-- [email protected]
> | | +-- [email protected]
> | | +-- [email protected]
> | | +-- [email protected]
> | | +-- [email protected]
> | | +-- [email protected]
> | | | `-- [email protected]
> | | +-- [email protected]
> | | `-- [email protected]
> | +-- [email protected]
> | +-- [email protected]
> | | `-- [email protected]
> | `-- [email protected]
> | `-- [email protected]
> +-- [email protected]
> | +-- [email protected]
> | +-- [email protected]
> | | +-- [email protected]
> | | +-- [email protected]
> | | +-- [email protected]
> | | `-- [email protected]
> | `-- [email protected]
> | +-- [email protected]
> | | `-- [email protected]
> | +-- [email protected]
> | `-- [email protected]
> +-- [email protected]
> +-- [email protected]
> +-- [email protected]
> +-- [email protected]
> +-- [email protected]
> +-- [email protected]
> +-- [email protected]
> +-- [email protected]
> +-- [email protected]
> +-- [email protected]
> +-- [email protected]
> +-- [email protected]
> +-- [email protected]
> +-- [email protected]
> +-- [email protected]
> `-- [email protected]
> npm WARN [email protected] No description
> npm WARN [email protected] No repository field.
> npm WARN [email protected] No license field.
> ---> 8be208b48383
> Removing intermediate container e763df440f84
> Step 9 : WORKDIR ../../
> ---> Running in a98eb90d44dd
> ---> b5d79ed23a6f
> Removing intermediate container a98eb90d44dd
> Step 10 : EXPOSE 3000
> ---> Running in cb6369afdb74
> ---> 690f1df45519
> Removing intermediate container cb6369afdb74
> Step 11 : CMD node main.js
> ---> Running in 009b3f8cb2d0
> ---> 515fcdc668d9
> Removing intermediate container 009b3f8cb2d0
> Successfully built 515fcdc668d9
> ▲ Storing image
> ▲ Deploying image
> ▲ Container started
> Deployment complete!
from meteor-now.
...
from meteor-now.
Deprecating in favor of meteor-hero.
from meteor-now.
Related Issues (20)
- Tests are failing on Windows
- MongoDB with Meteor 1.7 fails
- Error: Slash in host identifier HOT 6
- Meteor 1.7 mongo error HOT 4
- Support for GitHub Integration
- Use multi stage Docker builds HOT 5
- ▲ The built image size (417.0M) exceeds the 100MiB limit HOT 10
- Does meteor-now support now settings in now.json or package.json? HOT 5
- Does not support standard Mongo connection string HOT 2
- just saying thanks HOT 1
- Support METEOR_PACKAGE_DIRS HOT 1
- [FAQ] Will this work with any CI? HOT 1
- Way to change code without a full re-deploy HOT 1
- first run throws error HOT 1
- Compatibility with Now 2.0? HOT 28
- Possible to deploy without rebuilding if deploy failed HOT 1
- The property `features` is not allowed in now.json HOT 9
- Alias Support not workinb HOT 1
- Project name should be taken from package.json or now.json in priority
- [Error]: `Cannot read property '1' of null` HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from meteor-now.