<div dir="ltr">Yes, usually you have your info in an encrypted data bag, or you store the data bag directly in Chef, then during the Chef run data is rendered in a template. From that template, say /etc/environment, you can have you ENV variables set up and ready to be used.<div><br></div><div><span style="font-family:arial,sans-serif;font-size:12.7272720336914px">secrets.yml does not seem to be a big new feature. You can add you YAML file and load it at boot (Rails boot) time. What it important is not to store sensitive data in a GIT repository, unless it is encrypted.</span><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 23 September 2014 23:34, Phil Nash <span dir="ltr"><<a href="mailto:philnash@gmail.com" target="_blank">philnash@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Thanks for the answers so far everyone.<br><br>I'm interested in the methods you use to manage either secrets.yml, figaro's application.yml or dotenv's .env.production on production servers too. Do you do so using chef, as Seung-Hyo suggested (great link to that write up there, thanks) or some other way?<br><br></div>Thanks again, this is really interesting!<span class="HOEnZb"><font color="#888888"><br><br>Phil<br></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 23, 2014 at 7:18 PM, Siddharth Sharma <span dir="ltr"><<a href="mailto:svs@svs.io" target="_blank">svs@svs.io</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Rails 4.1 has secrets.yml <a href="http://edgeguides.rubyonrails.org/4_1_release_notes.html" target="_blank">http://edgeguides.rubyonrails.org/4_1_release_notes.html</a><div><br></div><div>For lower versions of Rails, I've been using figaro for years with no problems. I like to never have my production environment variables anywhere near my development environment, so I actually prefer not having an easy way to set heroku configs, etc. </div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>On Tue, Sep 23, 2014 at 11:43 PM, James McCarthy <span dir="ltr"><<a href="mailto:james@lety.co" target="_blank">james@lety.co</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div><div>Dotenv.</div><div><br></div><div><br></div>James McCarthy<br><br>Software Engineer<br><br>LetyCo - Analyse, Build, Deliver<br>Ruby/Rails software for London and the SouthEast.<br> <br>Mob: <a href="tel:07577006897" target="_blank">07577006897</a><br><br>Email: <a href="mailto:james@lety.co" target="_blank">james@lety.co</a><br><br><a href="http://lety.co/" target="_blank">lety.co</a><div><div><div></div><div><br></div><br><br>-------- Original message --------<br>From: Phil Nash <u></u> <br>Date:23/09/2014 19:06 (GMT+00:00) <br>To: London Ruby Users Group <u></u> <br>Subject: [LRUG] How do you manage secrets in Rails apps? <br><br><div dir="ltr"><div><div><div><div><div>Hi LRUG,<br><br></div>I've been thinking a lot recently about application secrets like API or database credentials and how they are stored in different environments for Rails apps. I was hoping that you lovely LRUG member could share how you deal with this yourself.<br><br>Currently I only tend to deploy apps to Heroku, so I use environment variables throughout the app, loaded in development/test environments with the <a href="https://github.com/philnash/envyable" target="_blank">envyable</a> gem, though <a href="https://github.com/laserlemon/figaro" target="_blank">figaro</a> would do the same job.<br><br></div>So, what I'm asking is, if you use environment variables for config in your applications how do you load them in both development and production environments?<br><br></div>Thanks,<br><br>Phil<br><br>--<br></div>Phil Nash<br></div>@philnash<br></div>
</div></div></div><br></div></div><span>_______________________________________________<br>
Chat mailing list<br>
<a href="mailto:Chat@lists.lrug.org" target="_blank">Chat@lists.lrug.org</a><br>
Archives: <a href="http://lists.lrug.org/pipermail/chat-lrug.org" target="_blank">http://lists.lrug.org/pipermail/chat-lrug.org</a><br>
Manage your subscription: <a href="http://lists.lrug.org/options.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/options.cgi/chat-lrug.org</a><br>
List info: <a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br>
<br></span></blockquote></div><br></div>
</blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Chat mailing list<br>
<a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a><br>
Archives: <a href="http://lists.lrug.org/pipermail/chat-lrug.org" target="_blank">http://lists.lrug.org/pipermail/chat-lrug.org</a><br>
Manage your subscription: <a href="http://lists.lrug.org/options.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/options.cgi/chat-lrug.org</a><br>
List info: <a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Riccardo Tacconi<br><br><a href="http://github.com/rtacconi" target="_blank">http://github.com/rtacconi</a><br><a href="http://twitter.com/rtacconi" target="_blank">http://twitter.com/rtacconi</a></div>
</div>