-
Notifications
You must be signed in to change notification settings - Fork 10
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
config.json file relative to process.cwd() #88
Comments
This makes As far as I know cipherlayer doesn't work as a dependency, right? If so, there should be a way to separate standalone and dependency. If you make a PR, create a |
thats the same solution I was thinking on |
in fact I was in the middle of that refactor when you did the lint one and then run out of time merging things... :) |
I will make the pull request with that aproach El jueves, 3 de marzo de 2016, Luis Mesas [email protected]
Alejandro González [image: Intelygenz] http://www.intelygenz.com/ |
Ok I wait then 👍 El jueves, 3 de marzo de 2016, Alejandro González Rodrigo <
Alejandro González [image: Intelygenz] http://www.intelygenz.com/ |
@guumaster can you explain that issu that will happen on imports to avoid it now? |
we should solve this issue in a way that cipherlayer service gets the options from the container project on launch instead of searching them on a file |
Well the But I've always thought that I only know a very few packages that depends on |
All paths to config.json should be relative to process.cwd() otherwise when using cipherlayer as a dependency the config.json file is not found in the project root, instead you need to put it in the node_modules directory inside cipherlayer.
In the commit commit all references to config.json was changed to be relative to chiperlayer.
Is there a reason to not make the config.json relative to process.cwd() instead of cipherlayer? if not i can make a pull request to change them again.
The text was updated successfully, but these errors were encountered: