Hacker Newsnew | past | comments | ask | show | jobs | submit | laserlemon's commentslogin

After a lengthy fight, I finally found a semi-sane way to manage multiple user profiles in Git. It's not nearly as easy as it should be…


Thank you! And I completely agree that secrets.yml is a win.


I'm really surprised I don't see more Emoji in HN post titles!


Thanks! Updated.


No, it's not. The idea is that your should be able to (hypothetically) open source your app at any time without compromising any sensitive information.


Figaro is certainly usable without Heroku. It added some Heroku conveniences later in life, but is built to simply populate ENV while keeping source control clean.


Good to know. I suppose for all cases where I'm deploying to non-Heroku servers I'd probably still use secrets.yml just because it's built into 4.1.


Makes sense, now that it's the new convention. Thanks for the comment!


Thanks. Quick and dirty is the key. And Airbrake is great for failures, but does it support uptime monitoring like Dead Man's Snitch does?


no, but I dont care if it's up as long as its not down :)

which, of course, leaves me hanging if the job queue is just not running, but thats monitored with runit which will issue an error if the service fails to start.


Not quite because the summary could change to nil, but it brings up a good point. There's often a better way in Rails, but &&= is native Ruby so it's especially useful in non-Rails applications.


Thank you for pointing this out. Addressed in the comments: http://collectiveidea.com/blog/archives/2011/06/21/the-billy...


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: