On a client project, we had recently installed capistrano-campfire to get notifications in our Campfire chatroom whenever a deployment takes place.
Unfortunately I kept getting
SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed (OpenSSL::SSL::SSLError)
when I tried deploying. There’s nothing quite like starting the year with SSL issues…
According to this article the problem
… comes from the fact that the new Ruby 1.9 installation doesn’t find the certification authority certificates (CA Certs) used to verify the authenticity of secured web servers.
I my case, I was using Ruby 1.8 (well, REE) on OS X Snow Leopard, but the problem - and solution - was the same nevertheless.
Dear Open Source Software
I don’t think I have ever written you before, but there is something I wanted to get off my chest.
I just wanted to let you know, that you rock! Just the other day, you saved my customer a bunch of money - and made me look like a hero.
Okay, I realize you only did so because I had done part of the work already. And I am probably giving you credit for something you didn’t really do, but thanks to you a team of strangers had implemented features I needed and given them back to me.
Also, the way you enable people I have never heard about to take something I have created and transform into something they can use, is mind boggling.
Thanks.
Yours, Jakob
PS: I know, I know… I don’t contribute often enough, and I will some day, I promise. Soon.
There are basically two kinds of deadlines: Real, and Arbitrary.
Real deadlines are those necessitated by some external, unchangeable event. For example legislation, the company running out of money, the CEO having to get up in front of the world press and announce the product, or a marketing campaign kicking off.
Just because I can never remember how to do this:
psql my_database -c "COPY (SELECT stuff FROM my_table) TO STDOUT CSV" > my_file.csvWorks in at least PostgreSQL 8.4.
Some third party systems needs to send requests to your web application in order to work.
Facebook fetches the actual application, Chargify notifies you of subscription changes, payment gateways tell you the transaction has been accepted.
That’s fine in production where you have a public facing webserver running, but when you’re developing locally you have to jump through a few hoops.
My parents have a digital camcorder. A week long vacation with said camcorder, my parents, and their only grandchild produces a fair amount of raw footage. Before we headed back home after the vacation I wisely snapped up all the footage from their camera hoping to eventually run it through iMovie.
Turns out their camcorder stores its clips in MTS/AVCHD format, and I didn’t grab all the fluff^Wnecessary files. As a result iMovie ‘11 cannot import the MTS video clips.
Life, Movies, Software, Technology , Read the full entry , 1 comments
While the concept of writing native Mac apps in Ruby definitely appeals to me, I must say the experience isn’t quite as easy as I was looking for.
After writing my last post I realized that what I had thought to be the path of least resistance, wasn’t. And while I knew I’d run into resistance with XCode and Objective-C as well, at least I’d be doing things the “proper” way and learning new stuff.
So I fired up XCode once again and set out to write a Mac application. The following is a bunch of notes and stray thoughts I scribbled down during those first hours - my first (well, fourth) impressions of developing iApps coming from Ruby.
I spent some time over the weekend playing around with MacRuby and HotCocoa, trying to put together a simple Mac application.
Getting MacRuby and HotCocoa running on Snow Leopard wasn’t entirely as easy as it should have been, though. Here are some of the hoops I jumped through.
Yesterday marked the 5 year anniversary of Copenhagen Ruby Brigade. Five years ago, I was part of founding that group. Five years, imagine that.
Back then, you could have heard me claim I knew all the Ruby developers in Denmark. While probably an exaggeration, it wasn’t far from the truth. Thankfully that is no longer the case. Yesterday, as I was sitting in the conference room at Podio looking at the other people present, I realized I didn’t know half of them. This got me thinking about how far we’ve come in the danish Ruby community over the last years.
Copenhagen.rb, Programming, Technology , Read the full entry , 5 comments
If you have ever tried to integrate with e-conomic you’ll likely recognize that their API comes out pretty high on the How to make a crappy API checklist.
Luckily, if you’re using Ruby, you can now use the r-conomic gem to handle SOAP and the other tedious bits for you.
I’ll let the README do the talking while I head on over to my Working With Rails profile and finally check off the “Has published a Ruby gem” checkbox.
Programming, Projects, Software , Read the full entry , 1 comments