-
-
Notifications
You must be signed in to change notification settings - Fork 288
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
Any npm packages that could use the same secrets? #284
Comments
@vfonic Figaro 2.0 (in development) adds a I'm not very familiar with Node.js development but |
That might work! I'm curious how it would work after deployment. 🤔 I'm eager to be the beta tester if that helps! :) |
I'm also very open to the creation of a JS Figaro sidecar (by somebody else! 😜), although I might suggest avoiding replicating Figaro v1 at this point, in favor of v2. |
@laserlemon Is there a better way to handle this please? (ie loading application.yml/figaro envs in webpack) Also can you share more details on how to do it with figaro exec please? |
I have a rails + webpacker project and I need to share some ENV vars between rails and webpacker (webpack/node).
It works great if I use 'dotenv-rails', but I prefer 'figaro' and its "use one file, never commit it and it's YAML" philosophy.
I also like ease of use of pushing ENV vars to heroku.
Is there some npm package that I can use, like 'dotenv', that will be able to read the secrets from
config/application.yml
? Should we build one? Maybe we could just fork 'dotenv' and have it parse YAML instead of reading in the "plain text" key=value pairs from multiple dotfiles.What do you think?
The text was updated successfully, but these errors were encountered: