- the reserved context is create and set at init time by the LodelContext.init method
- allows to use lodel libs will loading
- no special features implemented yet

- updated scripts etc
- make tests pass

Method is now disabled in MONOSITE mode

The server is listening, fork on new request, and then loads the context from URL.
Now we have to call properly the webui plugin in order to answer the request

- Replaced some "hidden" import with LodelContext.expose_modules calls
 - in some functions of Setting, Plugin, validator
 - in loader.py (temporary version)

In this state the tests runs (151 success), I'm able to run an instance (from debian package using slim) in MONOSITE mode and in MULTISITE mode by creating and loading a context in the loader.

Add the lodelsites directory to the autotools chain. Note : for the moment it's a dirty POC, we have to do it in a cleaner way...

Theorically all of those imports were tested by unit testing, but we've got no inssurance about that.
And even if unit tests had check for syntax errors, all pieces of code were not tested. We cannot
be sure that an import was missed or forgotten...

Test passes

Changed the exposure specs to allow giving an alias for an object when importing using the from x import y,z form

Addapted to links withou _blank target

Removed useless readonly property on some fields

When not found return None and do not try to run len() on None

Add master = true to uwsgi.ini

Add the custom message provided by HttpException to the template

Pymongo do not handles sets as value. We have to cast them into lists
done only in update for the moment...

Return an instance and not a list of len 1 anymore

In construct and check data

Add the possibility to give a fixed name to instances created by mass_deploy