First attempt at gemifying ecrire
Moving things around
First working version of the gem.

This commit includes way too much stuff to be listed here but I rather
talk about the goal behind this commit.

First of all, Ecrire can now launch a server by using the following
syntax in irb (given that the gem is installed):

require 'ecrire'; Ecrire.launch!

Ecrire::Application is a direct descendant of Rails::Application and
this is the app that is launched. When Ecrire.launch! is called, the app does a few
things:

- Include all the necessary gems for Ecrire to work
- Register a new railtie in lib/ecrire/themes/railtie.rb
- Configure the application throught lib/ecrire/config/environment.rb
- Launch the server through Rack::Server at port 3000 and host 0.0.0.0
  (localhost)

One thing that is VERY different from a normal application is how
Ecrire::Themes::Railties uses initializers to allow for themes to be
selected.

Ecrire comes with a default theme and controllers and an admin
interface. The admin & controller are the only things that cannot be
customized by the user through different themes.

For everything else, Ecrire looks at the current working directory from
where Ecrire.launch! was called and try to locate database.yml which it
will parse like you'd expect. It then parses secrets.yml and locate the
:theme key. If it's set, Ecrire will load that theme. If not, it will
use the default theme.

A custom theme is defined as follow:

In your working directory, you need to have the following folder
structure:

helpers/{theme_name}/*
assets/{theme_name}/javascripts
assets/{theme_name}/stylesheets
decorators/{theme_name}/*
views/{theme_name}/*
secrets.yml
database.yml

I believe that those 2 yml could probably be moved to a config/ folder
to follow Rails' structure (no need to customize everything)
Added a binary file that will be used by the user
Updated gemspec to depend on everything I need.

This is problematic as it makes everything boots PAINFULLY slow. This
should be sped up somehow. One solution would be to have a Gemfile on
the user's folder and then let bundler load the gems as it seems to be
faster (Unless my test was broken).
This commit is the most recent attempt at building what ecrire should be
like

The goal here is to have a standalone application that wraps around
rails and provides a simpler structure with a default theme and
obviously and administration panel. The goal is to have a user only
install ruby and postgresql and be set with a blog
Delete obsolete files
Added back a missing requirement
Last big changes commit, explanation below

First, I reintroduced Warden's configuration to environment.rb

Then, I removed all the dependency in the gemspec as it slows down the
boot sequence too much for it to be any usable when developing on
Ecrire.

Most important iteration is I18n working now. I added a recursive path
so raisl will look at all the files in locales.
Modified db_dir default location to point to user'

Because schema.rb is a configuration setting set for a giving instance,
it should be saved in the user's directory
Removed obsolete files
Removed bundle! as it won't be needed and included version
Administration shouldn't try to load post by their slug

If there's no slug, the admin panel becomes broken. I don't know if it's
mandatory yet so I just remove it for now.
Allow for database creation if it does not exist
Do not retry indefinitely
Fixed some model issue that was caused by previous misunderstandings