We need to bring our own bootstraps because we're using cutoms version of the lib (reason why we have the less files in /doc/), so we can't rely on saas-botstrap.
I know this lacks: • UI (you need to setup using rails console first) • Documentation (no one knows how to setup this but me) • Specs (lots of them) • Refactoring (I already know how to do it) Reasons why I'm pushing a so ugly feature / code are simple: • I need to play it in real life to fine tune the feature. • If we wait for a feature to be perfect before we push it, we'll never push it Hopefully, I have lots of time in a lost French countryside to polish it.
…hen needed. This won't hurt anyone and I'm really fed up with having constant Gemfile conflict because my theme needs hpricot to run.
…d a Travis specific gemfile
…flaw. 2013-03-12 - Remote code execution If a URL is from an untrusted source, commands can be injected into it for remote code execution with the ; character. Affected versions: All Identifier: CVE-2013-2616 Sources: http://vapid.dhs.org/advisories/minimagick.html http://direct.osvdb.org/show/osvdb/91231
Sam MySQL Ruby is an UTF-8 compliant port of the classic Mysql gem.
…eate zip and tar gz archives. Need to write down new documentation to take this into account