How I'm going to land my dream job

How I'm going to land my dream job

Neural net training fail

Neural net training fail

Pow + SSL without the hassle

Pow + SSL without the hassle

Using machine learning to rank search results (part 1)

Using machine learning to rank search results (part 1)

Using machine learning to rank search results (part 2)

Using machine learning to rank search results (part 2)

Managing complexity in Go

Managing complexity in Go

Remote work: an engineering leader's perspective

Remote work: an engineering leader's perspective

Running A/B tests on our hosting infrastructure

Running A/B tests on our hosting infrastructure

Optimising Redis storage, part two

Optimising Redis storage, part two

Every service is an island

Every service is an island

13 Jan 2014

0 min read

Dragonfly backed by ActiveRecord

If your app’s dynamic assets (user uploaded images for instance) weigh up to a few gigabytes, it can make sense to store them in the app’s database instead of another service (e.g. Amazon’s S3): your stack has one less dependency to care about, and backups get more complicated.

If you’re using the excellent dragonfly to manage and serve such assets, we’ve just released dragonfly-activerecord which lets you store assets to your app’s relational database.

It chunks and compresses files, is compatible with a variety of Rubies and databases, and is a drop-in replacements for Dragonfly’s default stores. It also plays nicely with Rack::Cache and/or a CDN for better performance.

This was reposted from HouseTrip’s developer blog.

This website is graciously hosted by Github Pages.

It's built using jekyll, markdown, bootstrap, bootstrap-sass, sass, haml plus a hefty dose of love and the benevolent tolerance of my significant other.

Unless otherwise stated, all content is © 2012-2014 Julien Letessier, all rights reserved. All code snippets are reusable free of charge under the terms of the MIT Licence.