News for hackers. Stuff that matters.
Re:Reminder: secret_token.rb is named so for a reason by joevandyk on Wednesday December 26, 2012 @05:15PM (#4971201)
Why don't more people keep configuration / api keys / etc in the database?

1. Your configuration is backed up along with your data.

2. You can share configuration with multiple applications easily.

3. Use postgresql's LISTEN/NOTIFY to tell your applications about new configuration changes in real-time.

4. Your configuration is as secret as your data.

Re:Reminder: secret_token.rb is named so for a reason by krapp on Wednesday December 26, 2012 @05:28PM (#4971261)
If you're vulnerable to a sql injection or something similar, though, then you've potentially made all of that data web accessible.
Re:Reminder: secret_token.rb is named so for a reason by joevandyk on Wednesday December 26, 2012 @05:37PM (#4971307)
If you are vulnerable to sql injection, you are completely screwed anyways.
Re:Reminder: secret_token.rb is named so for a reason by krapp on Wednesday December 26, 2012 @05:45PM (#4971346)
that's probably true.
Re:Reminder: secret_token.rb is named so for a reason by dice on Wednesday December 26, 2012 @06:39PM (#4971545)
Where do you store the configuration for where and how to access the configuration database?
Re:Reminder: secret_token.rb is named so for a reason by joevandyk on Wednesday December 26, 2012 @10:17PM (#4972184)
That's the only thing I keep as an env var (as DATABASE_URL: ie "postgres://monkey:pass@localhost/tanga_dev")