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

Building NPM packages inside npm-container doesn't work in production deployment #609

Closed
jykae opened this issue Nov 11, 2015 · 2 comments
Closed

Comments

@jykae
Copy link
Contributor

jykae commented Nov 11, 2015

Please stick to Meteor packages as much as you can. NPM packages must be installed manually after production build. I am automating the building process with Meteor Up, which reduces the amount of work a LOT. (Nginx, Node.js, MongoDB + all the configuration are done automatically).

Good thing is that currently we have only "elasticsearch" NPM package required.

@bajiat
Copy link
Contributor

bajiat commented Nov 12, 2015

To be checked whether the problem still persists with 0.2.0 alpha 1 release deployment.

@jykae
Copy link
Contributor Author

jykae commented Nov 15, 2015

Solved. Complete re-installation of NPM on my own machine fixed the problem.

@jykae jykae closed this as completed Nov 15, 2015
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

2 participants