Brakeman is great. I think it should check the Gemfile also. Seems like a good place for it. The opinion is mixed though.

https://github.com/presidentbeef/brakeman/issues/276

A complementary command-line tool would be fine too.

Anyone else having trouble getting "export OPENSSL_NO_DEFAULT_ZLIB=1" to work on Apache 2.2.22, CentOS 5.9?

I have tried it in /etc/sysconfig/httpd and /etc/init.d/httpd (in start) and SSL tools still report that compression is on.

Hm, I'm just on my phone now and going to bed but here's link from RH's bugzilla going into it, maybe it's of any help to you: https://bugzilla.redhat.com/show_bug.cgi?id=857051#c5

Can't say any more than that it works for us – we compile Apache ourself though for various reasons. But according to the link above it should work.

I'm not sure of the best way to go about it, but if all the dependency gems are also on Github, a script might be able to pull the SHAs from the right version of each dependency and return the proper entries for a Gemfile.

gemspecs/Gemfiles rarely list the gh repo, so you'll likely have to get it from a source which is probably rubygems. If it's compromised, they could update the gh repo location as well.

I guess, at least for the most common gems, there could be an independent list which maps gem names to their Github repos. Of course, that list would have to be trustworthy. It would be nice to solve that mapping problem anyway, because sometimes it's not entirely clear which Github repo is the official source for a project.

It seems like all the current hi res solutions are somewhat hacky. I recently did a project with foresight.js (https://github.com/adamdbradley/foresight.js) I like how it tries to estimate the connection speed before serving up a 2x image.

Can anyone point to a guide for using the web inspector in Safari 6? It looks like it could be powerful, but it is not as user-friendly as the Safari 5 and Chrome inspectors. It feels like a step back.

Has anyone figured out how to set a breakpoint in the actual page (not a .js file)? There are no line numbers in the inspector to click on. I complained to Apple. I also can't figure out how to add script files to the sources tab in the new webkit version of the inspector. Also clicking on the line numbers in the resources tab of the new webkit inspector no longer sets a breakpoint. I've had to go back to 5.x since I can't set breakpoints where I need to... Ideas?

Apple's documentation has been updated for Safari 6's new Web Inspector: http://developer.apple.com/library/safari/#documentation/app...

I got this informative error message: "Additional uncaught exception thrown while handling exception."

Looks good. I guess they beat Travis CI to the punch for testing private projects and taking payment for it. But it's Ruby only, at least right now. Maybe someday Github will just build this in with their 100 million.

They may do that - however running tests on every single push is not exactly resource free, and I have a hard time believing Github will offer it for free. And Semaphore's integration/UI seems pretty seamless already.

On a side note - I know some of the guys behind this - solid team that will go above and beyond to make you a happy customer if you sign up. I believe this alone could be a significant competitive advantage.

foresight.js looks more interesting since it takes the perceived connection speed into account when deciding to serve up 2x images. https://github.com/adamdbradley/foresight.js

That's pretty intelligent.