
2 min read
Giving Rails back to the app
0.18.0 hands every Rails setting, path and name back to the site. Along the way: a closed upload endpoint, a constant that resolved to the wrong class, and a migration clash only a real generator could find.
Topic
The thinking behind the way Nibble is built.
Fresh from the oven 0.18.1 folds Nibble's thirty-six migrations into one per table, each creating its table as it is now. The catch was the order: foreign keys decide which migration has to run last.
2 min read
Read the post
2 min read
0.18.0 hands every Rails setting, path and name back to the site. Along the way: a closed upload endpoint, a constant that resolved to the wrong class, and a migration clash only a real generator could find.

1 min read
0.16.0 moved all of Nibble into vendor/nibble and made upgrades a matter of swapping that folder. Here's why merging our git history into every site's repository had to go.

2 min read
Nibble 0.1.0 is out. A CMS you run as your own Rails application, where the shape of your content lives in YAML beside your code and everything else is ordinary Rails.