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

Support METEOR_PACKAGE_DIRS #128

Open
eric-burel opened this issue Sep 12, 2018 · 1 comment
Open

Support METEOR_PACKAGE_DIRS #128

eric-burel opened this issue Sep 12, 2018 · 1 comment

Comments

@eric-burel
Copy link

Hi,

I rely a lot on the METEOR_PACKAGE_DIRS to separate reusable packages I develop from specific app package. Currently, this variable seems to be only taken into account by Meteor Up, and I know that it is ignored by the Meteor Buildpack for Heroku.

I did not test Meteor Now yet because I am not sure if it is correctly handled, so here are my questions:

  • is METEOR_PACKAGE_DIRS taken into account during build, and if yes is there something to do to set it up?

  • if no, do you think it is possible to allow using this env variable when using Meteor Now? Basically you need it to be set when building the Meteor app, and of course to be able to access the relevant packages during this build. So it may imply to build on the users machine I think, I am not sure how it is handled by Meteor Up currently.

@Apollinaire
Copy link

I tested this with METEOR_PACKAGE_DIRS set in my .bashrc and it worked.
It will also probably work if you set it every time with the command:

env METEOR_PACKAGE_DIRS="/path/to/my/pckgs:/other/path" meteor-now

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