On Thursday we attended the Ruby User Group (RUG::B) April meetup at Kauferportal. With 3 normal talks and 5 lightning talks the program was pretty packed. Good thing I summarized it for you:
Migrating databases like a Pro!
Hans Hasselberg, responsible for Ops at 6wunderkinder, talked about migrating databases. And not just your usual db/migrate, but actually moving an entire database to another server. 6wunderkinder uses AWS with PostgresSQL type db.m2.2xlarge. Preparing to move to a smaller server and improving efficiency (and thus optimizing for scalability), Hans had to simulate production load to make sure the new, tinier server won’t die under its load. How? By enabling query logging maybe, but that would mean touching the database. Or one could sniff the traffic. Say hello to
<a href="https://ngrep.sourceforge.net/" target="_blank">ngrep</a>. With a one time operation and a fixed set of operations however, you might miss an important set and you can’t compare how the new database behaves as apposed to the old one. (more…)
In this post we will generate PDF’s with Ruby, exploring the exemplary use case of creating customer invoices. In order to output PDF’s from your (custom) billing system, you’ll need a library that exports PDF’s. There are different ways to achieve HTML to PDF conversion in Ruby. Let’s take a closer look.
HTML to PDF libraries
Two major players in this field are PDFlib and Prawn. PDFlib is a commercial library, and as such more advanced than Prawn. You’ll find table configuration and formatting to be a helpful feature. PDFlib has many more bindings, with support for PHP, Perl, Python, Ruby, Java, .NET and C++/C.
Yet, the Prawn ‘API’ will feel more natural to a Rubyists The PDFlib extension doesn’t feel like Ruby most of the time, it’s just a wrapper for the normal PDFlib C calls. Plus: Prawn is open source (and thus free of charge).
Yesterday, little after seven-thirty, the Emacs Berlin user group came together for the very first time. As a Textmate-turned-Atom user myself, I was nothing but ears for the stories about what I’ve learned to be one of the most powerful tools out there.
The format of the meetup is an interesting one. Everybody is expected to show something to the rest of the group and you get up to 10 minutes to do so. Plus, you’re requested to prepare notes beforehand and share the link to your gist on the mailing list, so people can easily follow along on their own machine.
I diligently wrote down all tips shared at what is already jokingly referred to as “the biggest yak shaving meetup in town”. Please refer to the official notes, if you distrust my judgement as an Atom user. Really, it’s ok.