HN user
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.
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.
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.
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.
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.
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