Posted by Kenneth Kalmer
on July 02, 2008
Strange days we live in, especially when our browsers trip of bugs in encryption libraries on the servers… David Smalley neatly pointed out how upgrading OpenSSL to at least 0.9.8h solves the cryptic Firefox 3 SSL errors we’ve been seeing on some our sites.
Secure Connection Failed An error occurred during a connection to xyz-abe.com SSL received an unexpected Change Cipher Spec record. (Error code: ssl_error_rx_unexpected_change_cipher)
Currently the package in question is still masked in gentoo, so upgrade as follows:
# echo ‘=dev-libs/openssl-0.9.8h-r1′ >> /etc/portage/package.unmask
# emerge -av openssl
Once done, follow the instruction given by portage to rebuild the packages still using the old versions of OpenSSL.
Thanks David
Posted by Kenneth Kalmer
on June 02, 2008
Apart from my Rubyforge email alert, this seems to have pretty much go unnoticed so far. Think everyone was too busy attending RailsConf 2008.
Rails 2.1 @ Rubyforge
Rails 2.1 @ github
Enjoy!
Posted by Kenneth Kalmer
on May 26, 2008
I checked up on ActiveRecord::Tableless and saw a fork that had some promising changes in, so I set out to pull those changes back to my repo. Seemed simple enough, I followed Steven Bristol’s steps and it worked.
The changes made by Peter Wagenet were simple and very useful, thanks Pete!
I’ll start working on specs for the project closer to the end of the week, for now my focus is on getting BIND DLZ on Rails ready for its first public appearance.
Posted by Kenneth Kalmer
on May 15, 2008
Surely your Rails app flies, no request takes longer than 60 seconds to complete, ever. You’ve proven that Rails can scale and all that jazz. Surely you’ve really spent the time to read the nginx wiki and customize Ezra’s nginx.conf to such a degree that you can handle thousands of concurrent requests at any given time. You know, Rails scales…
Now some of us develop fairly intricate systems using Rails. Systems that have long running reports, or systems that connect to other systems to execute commands, or obtain information. Whatever the reason, somethings just can’t complete within 60 seconds, and if your users understands the complexity of the background tasks they’ll quite happily press a button and go make coffee while the server crunches away at the reports.
I head one such project, and had the most interesting issue I just solved. And it involved reading a lot on nginx’s fine print…
Continue reading…
