guacamole 0.0.1 → 0.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: d38e9050d4e439c666b9bdee7a12b7798afd945a
-  data.tar.gz: 8b007745d612877f577f97135b438788ac89067f
+  metadata.gz: 65f6f1c73821edaf59fae8fea0554389f9426a9c
+  data.tar.gz: 4eb7f2737b833d830680804d0681b39612e4e27d
 SHA512:
-  metadata.gz: 9d807363c5aa0f0ab0fef05d0fca81ce5806b7ac33d199997e5ab50f2a7aa6026736305f4768c8015a2e0c79b889c5400898b504ce98f0189f16720e79cf1361
-  data.tar.gz: 5e75106be148ca5af2147e985266320f5268e72622c4de98a1d54b38528a816b2bd4ce3110963d0769c106b48619dc97058eb611192c30bcaf8fc05555f4dcd7
+  metadata.gz: 3d73b44a1c7111fe19d662f3ede415f2b574d1502b90644050e029ae330869ceec50b32d621d8863c8b45f0ded991997a6753701cfeb4ef976774f94ab9ea63d
+  data.tar.gz: 95bed05003e2f5a2796b7e53b03a9c7620e2a325b3b47697be15e451c8be813ecd1c45eaffb0c4c1113fa0777e2d1d2146dded64698bdb7638252e0db265f298

data/.gitignore

@@ -16,3 +16,4 @@ spec/reports
 test/tmp
 test/version_tmp
 tmp
+cache

data/{config/rubocop.yml → .hound.yml}

@@ -6,9 +6,7 @@ AllCops:
     - 'Gemfile'
     - 'Gemfile.devtools'
   Excludes:
-    - '**/spec/setup/**'
-    - '**/vendor/**'
-    - '**/benchmarks/**'
+    - !ruby/regexp /spec\/setup/
 
 # Avoid parameter lists longer than five parameters.
 ParameterLists:
@@ -31,15 +29,6 @@ SignalException:
   # Valid values are: semantic, only_raise and only_fail
   EnforcedStyle: only_raise
 
-# Do not force public/protected/private keyword to be indented at the same
-# level as the def keyword. My personal preference is to outdent these keywords
-# because I think when scanning code it makes it easier to identify the
-# sections of code and visually separate them. When the keyword is at the same
-# level I think it sort of blends in with the def keywords and makes it harder
-# to scan the code and see where the sections are.
-AccessControl:
-  Enabled: false
-
 # Limit line length
 LineLength:
   Max: 120

data/.ruby-version

@@ -1 +1 @@
-ruby-2.0.0-p247
+ruby-2.0.0-p353

data/.travis.yml

@@ -13,6 +13,8 @@ env:
   - ARANGODB_DISABLE_AUTHENTIFICATION=true VERSION=1.4.0-beta2
 matrix:
   allow_failures:
+    - rvm: jruby-19mode
     - rvm: ruby-head
     - rvm: jruby-head
+    - rvm: rbx-19mode
 script: "bundle exec rake ci"

data/.yardopts

@@ -0,0 +1 @@
+--markup markdown

data/CONTRIBUTING.md

@@ -2,12 +2,12 @@
 
 When you want to write code for the project, please follow these guidelines:
 
-1. **Claim** the ticket: Tell us that you want to work on a certain ticket, we will assign it to you (We don't want two people to work on the same thing ;) )
-2. **Fork** your feature branch from the `development` branch (not the `master` branch)
+1. **Claim** the ticket: Tell us that you want to work on a certain ticket, we will assign it to you (We don't want two people to work on the same thing :wink: )
+2. **Fork** your feature branch from the `master` branch
 3. Write an **acceptance test**: Describe what you want to do (our acceptance tests touch the database)
 4. **Implement** it: Write a unit test, check that it fails, make the test pass – repeat (our unit tests don't touch the database)
 5. Write **documentation** for it.
-6. Check with `bundle exec rake ci` (you need to have ArangoDB running for that) that everything is fine and send the pull request to the `development` branch :)
+6. Check with `bundle exec rake ci` (you need to have ArangoDB running for that) that everything is fine and send the pull request to the `master` branch :)
 
 ## Setup
 

data/Gemfile.devtools

@@ -4,21 +4,23 @@ group :development do
   gem 'rake',  '~> 10.1.0'
   gem 'rspec', '~> 2.14.1'
   gem 'yard',  '~> 0.8.7'
+
+  platform :rbx do
+    gem 'rubysl-singleton', '~> 2.0.0'
+  end
 end
 
 group :yard do
-  gem 'kramdown', '~> 1.2.0'
+  gem 'kramdown', '~> 1.3.2'
 end
 
 group :guard do
-  gem 'guard',         '~> 1.8.1'
-  gem 'guard-bundler', '~> 1.0.0'
-  gem 'guard-rspec',   '~> 3.0.2'
-  gem 'guard-rubocop', '~> 0.2.0'
-  gem 'guard-mutant',  '~> 0.0.1'
+  gem 'guard',         '~> 2.4.0'
+  gem 'guard-bundler', '~> 2.0.0'
+  gem 'guard-rspec',   '~> 4.2.6'
 
   # file system change event handling
-  gem 'listen',     '~> 1.3.0'
+  gem 'listen',     '~> 2.5.0'
   gem 'rb-fchange', '~> 0.0.6', require: false
   gem 'rb-fsevent', '~> 0.9.3', require: false
   gem 'rb-inotify', '~> 0.9.0', require: false
@@ -32,16 +34,26 @@ end
 group :metrics do
   gem 'coveralls', '~> 0.7.0'
   gem 'flay',      '~> 2.4.0'
-  gem 'flog',      '~> 4.1.1'
+  gem 'flog',      '~> 4.2.0'
   gem 'reek',      '~> 1.3.2'
-  gem 'rubocop',   '~> 0.14.1'
-  gem 'simplecov', '~> 0.7.1'
-  gem 'yardstick', '~> 0.9.7', git: 'https://github.com/dkubb/yardstick.git'
+  gem 'simplecov', '~> 0.8.2'
+  gem 'yardstick', '~> 0.9.9'
+
+  # platforms :mri do
+  #   gem 'mutant', '~> 0.3.6'
+  # end
 
   platforms :ruby_19, :ruby_20 do
-    gem 'mutant', git: 'https://github.com/mbj/mutant.git'
     gem 'yard-spellcheck', '~> 0.1.5'
   end
+
+  platform :rbx do
+    gem 'json',               '~> 1.8.1'
+    gem 'racc',               '~> 1.4'
+    gem 'rubysl-logger',      '~> 2.0.0'
+    gem 'rubysl-open-uri',    '~> 2.0.0'
+    gem 'rubysl-prettyprint', '~> 2.0.2'
+  end
 end
 
 group :benchmarks do

data/Guardfile

@@ -3,7 +3,7 @@ guard 'bundler' do
   watch(/^.+\.gemspec/)
 end
 
-guard 'rspec', spec_paths: 'spec/unit' do
+guard 'rspec', spec_paths: ['spec/unit'] do
   watch(%r{spec/.+\.rb})
   watch(%r{lib/guacamole/(.+)\.rb$}) { |m| "spec/unit/#{m[1]}_spec.rb" }
 end

data/README.md

@@ -1,24 +1,31 @@
+[![RubyDoc](http://img.shields.io/badge/📄-RubyDoc-be1d77.svg)](http://rubydoc.info/gems/guacamole/frames)
+[![Build Status](http://img.shields.io/travis/triAGENS/guacamole.svg)](https://travis-ci.org/triAGENS/guacamole)
+[![Code Climate](http://img.shields.io/codeclimate/github/triAGENS/guacamole.svg)](https://codeclimate.com/github/triAGENS/guacamole)
+[![Gem Version](http://img.shields.io/gem/v/guacamole.svg)](https://rubygems.org/gems/guacamole)
+
 # Guacamole
 
-| Project         | Guacamole
-|:----------------|:--------------------------------------------------
-| Homepage        | https://github.com/triAGENS/guacamole
-| Documentation   | **TODO: Add RubyDoc URL**
-| CI              | [![Build Status](https://travis-ci.org/triAGENS/guacamole.png)](https://travis-ci.org/triAGENS/guacamole)
-| Code Metrics    | [![Code Climate](https://codeclimate.com/github/triAGENS/guacamole.png)](https://codeclimate.com/github/triAGENS/guacamole)
-| Gem Version     | **TODO: Add Badge Fury Badge**
-| Dependencies    | [![Dependency Status](https://gemnasium.com/triAGENS/guacamole.png)](https://gemnasium.com/triAGENS/guacamole)
-| Ready Stories   | [![Stories in Ready](https://badge.waffle.io/triagens/guacamole.png?label=ready)](https://waffle.io/triagens/guacamole)
+Guacamole is an Object Document Mapper (ODM) for the multi-model NoSQL database [ArangoDB](https://www.arangodb.org/). Its main goal is to support easy integration into Ruby on Rails but will likely work in other Rack-based frameworks as well. There are a couple of design goals behind Guacamole which should drive all our development effort:
+
+  * Easy integration on the View layer (i.e. form builders)
+  * Reflect the nature of NoSQL in general and ArangoDB in particular
+  * Focus on long-term maintainability of your application
+
+While the first two points don't need any further explanation we want to lay out the motivation behind the last point: 'Ease of use' is very important to us, but we made some fundamental decisions which will cause a stepper learning curve than other libraries, notably ActiveRecord. If you have a traditional Rails background you will find some things quite different. We decided to go this direction, because we think it better suites the features of ArangoDB. Applying the semantics of a different environment maybe helps with the first steps but will become problematic if you further advance in your understanding of the possibilities.
 
-Guacamole is an ODM for ArangoDB that offers integration for Ruby on Rails.
+That said we still think we provide a sufficient API that is quite easy to get hold of. It is just a bit different from what you were doing with ActiveRecord.
 
-All tests run on Travis CI for the following versions of Ruby:
+For a high-level introduction you can also refer to [this presentation](https://speakerdeck.com/railsbros_dirk/how-to-make-guacamole).
 
-* MRI 1.9.3 and 2.0.0
-* Rubinius 1.9 mode
-* JRuby 1.9 mode
+## Getting started (with a fresh Rails application)
 
-## Installation
+Since Guacamole is in an alpha state we suggest you create a new Rails application to play around with it. We don't recommend adding it to a production application.
+
+First of all create your shiny new application, without ActiveRecord of course:
+
+```shell
+rails new -O $my_awesome_app
+```
 
 Add this line to your application's Gemfile:
 
@@ -26,47 +33,261 @@ Add this line to your application's Gemfile:
 gem 'guacamole'
 ```
 
-And then execute:
+And then install the new dependencies:
+
+```shell
+bundle install
+```
+
+### Configuration
+
+After you created the application and installed the dependencies the first thing you need is a configuration file. The database connection is pretty much configured as expected: With a YAML file. Luckily you don't have to create this file by yourself but you can use a generator to do it for you:
 
 ```shell
-bundle
+bundle exec rails generate guacamole:config
+```
+
+This will create a default configuration at `config/guacamole.yml`:
+
+```yaml
+development:
+  protocol: 'http'
+  host: 'localhost'
+  port: 8529
+  password: ''
+  username: ''
+  database: 'pony_blog_development'
 ```
 
-Or install it yourself as:
+After you created a configuration file you can create the database as in any other Rails project:
 
 ```shell
-gem install guacamole
+bundle exec rake db:create
 ```
 
+If you're using Capistrano or something else make sure you change your deployment recipes accordingly to use the `guacamole.yml` and not the `database.yml`. Of course you would want to add [authentication](https://www.arangodb.org/manuals/2/DbaManualAuthentication.html) for the production environment. Additionally you may want to consider putting ArangoDB behind a SSL-proxy or use the [built in SSL support](https://www.arangodb.org/manuals/2/CommandLine.html#CommandLineArangoEndpoint).
+
+Now where everything is set up we can go ahead and create our application's logic. Before we give you some code to copy and paste we first give you a general usage and design overview.
+
 ## Usage
 
-There are two main concepts you have to be familiar with in Guacamole: Collections and models. Both of these are modules that you can mixed in to your classes:
+One of the key features of Guacamole is the implementation of the [Data Mapper Patter](http://martinfowler.com/eaaCatalog/dataMapper.html). This brings a lot of good things along, like
+
+  * Improved testability
+  * Separation of Concern and
+  * Easier to support database
features like embedded objects
+
+The gist of the pattern is you have two classes where you would have one when you use ActiveRecord: A `Collection` and a `Model`. The `Collection` is responsible for getting data from and writing data to the database. The `Model` represents the domain logic (i.e. attributes) and has no idea what a database is. Due to this you could far easier test the domain logic without a database dependency. But you have always two (or more) classes around. The following will introduce you to both those classes.
 
 ### Models
 
-Models are representations of your data. They are not aware of the database but work independent of it. A simple example for a model:
+Models are representations of your data. They are not aware of the database but work independently of it. Guacamole ships with a generator for models:
+
+```shell
+bundle exec rails generate model pony name:string birthday:date color:string
+```
+
+This will generate both a `Model` **and** a `Collection` (more on that later). If you don't want a `Collection` to be created just add the `--skip-collection` flag to the generator. The `Model` will be written to `app/models/pony.rb` and it will have the following content:
 
 ```ruby
-class Article
+class Pony
   include Guacamole::Model
 
-  attribute :title, String
-  attribute :comments, Array[Comment]
+  attribute :name, String
+  attribute :birthday, Date
+  attribute :color, String
+end
+```
+
+Since the database doesn't know anything about a schema we must define the attributes in the model class itself. At the same time this has the advantage to open the model class and see what attributes it has. An attribute is defined with the `attribute` class method. We use [Virtus](https://github.com/solnic/virtus) for this purpose. Basically you add give the attribute a name and a type. The type have to be the actual class and **not** a string representation of the class. You could even define collection classes:
+
+```ruby
+class Pony
+  include Guacamole::Model
 
-  validates :title, presence: true
+  attribute :type, Array[String]
 end
 ```
 
-This example defines a model called Article, which has a title represented by a String and an array of comments. Comment in this case is another `Guacamole::Model`. The `Model` mixin will also add validation from ActiveModel to your model – it works as you know it from ActiveRecord for example.
+For further reference what is possible please refer to the [Virtus documentation](http://rubydoc.info/gems/virtus/1.0.2/frames). One thing to add here, whenever you assign a value to an attribute Virtus will perform a type coercion:
+
+```ruby
+pinkie_pie = Pony.new
+pinkie_pie.color = :pink
+# => "pink"
+pinkie_pie.type  = "Earthpony"
+# => ["Earthpony"]
+```
+
+#### Timestamps
+
+We will automatically add time stamp columns to all models when you include `Guacamole::Model`. We eventually will make this configurable, but for now it is not.
 
-In a Rails application, they are stored in the `app/models` directory by convention.
+#### The ID of a model
+
+In ArangoDB a document has three internal fields: `_id`, `_key` and `_rev`. For a detailed explanation how these three work together please refer to the [ArangoDB documentation](https://www.arangodb.org/manuals/2/HandlingDocuments.html#HandlingDocumentsIntro). Within Guacamole we will always you the `_key` because it is enough the identify any document within a collection. Both the `_key` and `_rev` attribute are available through the `Guacamole::Model#key` and `Guacamole::Model#rev` attribute. You don't have to do anything for this, we will take care of this for you.
+
+Additionally you will find an `id` method on you models. This is just an alias for `key`. This was added for `ActiveModel::Conversion` compliance. You **should always** use `key`.
+
+#### Validations
+
+When including `Guacamole::Model` you will not only get the functionality of Virtus but some ActiveModel love, too. Besides the [`ActiveModel::Naming`](http://api.rubyonrails.org/classes/ActiveModel/Naming.html) and [`ActiveModel::Conversion`](http://api.rubyonrails.org/classes/ActiveModel/Conversion.html) module you will get [Validations](http://api.rubyonrails.org/classes/ActiveModel/Validations.html) as well. Thus you could just write something like this:
+
+```ruby
+class Pony
+  include Guacamole::Model
+
+  attribute :name, String
+  attribute :color, String
+
+  validates :color, presence: true
+end
+
+transparent_pony = Pony.new
+transparent_pony.valid?
+# => false
+transparent_pony.errors[:color]
+# => ["can't be blank"]
+```
+
+As the model doesn't know anything about the database you cannot define database-dependent validations here (i.e.: uniqueness). This logic has to be handled in the `Collection`. That said, we have no strategy how to model this in the `Collection`. If you have any idea about this we would love to hear about it.
 
 ### Collections
 
 Collections are your gateway to the database. They persist your models and offer querying for them. They will translate the raw data from the database to your domain models and vice versa. By convention they are the pluralized version of the model with the suffix `Collection`. So given the model from above, this could be the according collection:
 
 ```ruby
-class ArticlesCollection
+class PoniesCollection
+  include Guacamole::Collection
+end
+```
+
+As with the models we provide a generator to help you creating your collection classes. In most cases you won't need to invoke this generator due to the model generator already created a collection for you. But if for any reason you need another collection without a model you could do it like this:
+
+```shell
+bundle exec rails generate collection ponies
+```
+
+Currently your options what you can do with a collection are quire limited. We will eventually add more features, but for now you basically have this features:
+
+  * CRUD operations for your models
+  * Where the "Read"-part is limited to [Simple Queries](https://www.arangodb.org/manuals/2/SimpleQueries.html). But more on this later.
+  * Mapping embedded models
+  * Realizing basic associations
+
+For all the mapping related parts you don't have any configuration options yet, but have to stick with the conventions. Obviously this will change in the future but for now there more important parts to work on. Before we dig deeper into the mapping of embedded or associated models let us look at the CRUD functionality.
+
+#### Create models
+
+To create a model just pass it to the `save` method of the `Collection` in charge:
+
+```ruby
+pinkie = Pony.new(name: "Pinkie Pie")
+PoniesCollection.save pinkie
+# => #<Pony:0x124 …>
+```
+
+The `save` method will trigger model validation before writing it to the database. If the model is not valid `false` will be returned. All validation errors can be retrieved from the model itself. They are stored in `errors` attribute which is provided by `ActiveModel::Validations`.
+
+Every model has a `persisted?` method which will return `false` unless the model is saved to the database and thus has a `key` assigned.
+
+#### Update models
+
+Updating models is just the same as creating models in the first place:
+
+```ruby
+existing_pony.name = "Applejack"
+PoniesCollection.save existing_pony
+# => #<Pony:0x1451 …>
+```
+
+**Note**: As of today there is **no dirty tracking**. Models will always be updated in the database when you call `save` – no matter if they have changed or not.
+
+#### Delete models
+
+You can `delete` models from the database by either passing the model to be deleted or just its key. In both cases the key will be returned:
+
+```ruby
+PoniesCollection.delete existing_pony
+# => `existing_pony.key`
+```
+
+#### Retrieve models
+
+As mentioned before querying for models is quite limited as of now. We only support [Simple Queries](https://www.arangodb.org/manuals/2/SimpleQueries.html) at this point. You can perform the following basic operations with them:
+
+  * Getting a single model `by_key`
+  * Getting `all` models from a collection.
+  * Query models `by_example`. You can **only** perform equality checks with this.
+  * You can `skip` and `limit` the results
+
+You always need to start a query by either calling `all` or `by_example`. You could chain those with `skip` and `limit`. The query to the database will only be performed when you actually access the documents:
+
+```ruby
+some_ponies = PoniesCollection.by_example(color: 'green').limit(10)
+# => #<Guacamole::Query:0x1212 …>
+some_ponies.first
+# The request to the database is made
+# => #<Pony:0x90u81 …>
+```
+
+We're well aware this is not sufficient for building sophisticated applications. We're are working on something to make [AQL](https://www.arangodb.org/manuals/2/Aql.html) usable from Guacamole.
+
+### Mapping
+
+As the name "Data Mapper" suggests there is some sort of mapping going on behind the scenes. The mapping relates to the process of _mapping_ documents from the database to the domain models. 
+
+The `Collection` class will lookup the appropriate `Model` class based on its own name (i.e.: the `PoniesCollection` will look for a `Pony` class). Currently there is no option to configure this so you're stuck with our conventions (for now):
+
+  * Collections in ArangoDB are the plural form of the `Model` class name
+  * The `Collection` class is the plural form of the `Model` class name with the suffix `Collection`
+
+Without any configuration we will just map the attributes present in your domain model. If you retrieve a document from the database that contains other attributes then your domain model they will be silently discarded. To illustrate this imagine we have a document in the `ponies` collection which looks like this:
+
+```json
+{
+  "_key": "303",
+  "_rev": "1019391",
+  "name": "Applejack",
+  "color": "green",
+  "occupation": "Farmer"
+}
+```
+
+When we receive this document and map it against the above mentioned model there will be no `occupation` attribute be present:
+
+```ruby
+pony = PoniesCollection.by_key "303"
+pony.occupation
+# => NoMethodError: undefined method `occupation' for #<Pony:0x00000105fc77f8>
+```
+
+Currently there is not option to change the mapping of attributes. If you want to map more or less attributes you should create another model for that purpose.
+
+#### Associations
+
+Besides simple attributes we want to handle associations between models. To add an association between your models you have two options: __embedded__ and __referenced__.
+
+#### Embedded references
+
+If you go with the `embeds` option the embedded model will be stored within the **same** document in the database. The comments of a blog post are a good example where this can be handy. While the database will have only one document the domain can still know about a `Comment` and a `Post`. In this case you would end up with two models and one collection:
+
+```ruby
+class Comment
+  include Guacamole::Model
+
+  attribute :text, String
+end
+
+class Post
+  include Guacamole::Model
+
+  attribute :title, String
+  attribute :body,  String
+  attribute :comments, Array[Comment]
+end
+
+class PostsCollection
   include Guacamole::Collection
 
   map do
@@ -75,48 +296,124 @@ class ArticlesCollection
 end
 ```
 
-As you can see above, you don't need to explicitly state that you are mapping to the `Article` class, because this is the naming convention. But what does `map` do?
-
-In the block you provide to `map` you can configure things that should happen when you map from the raw data to the model and vice versa. In a document store like ArangoDB you can have nested data – so the JSON stored in ArangoDB's `articles` collection could look something like this:
+As you can see, from the model perspective there is nothing special about an embedded association. It is just another attribute on the `Post` class. How this is stored will be configured where it is handled: In the `PostsCollection`. Within the `map` block you put all the mapping related configuration. The `embeds` method will make sure that `Comment`s are correctly stored and received within the database. Be aware that embedded models will not have any `_key`, `_id` or `_rev` attribute. But they will have the time stamp attributes correctly populated. Within ArangoDB the resulting document will look like this:
 
 ```json
 {
-  'title': 'The grand blog post',
-  'comments': [
+  "_id": [...],
+  "_rev": [...],
+  "_key": [...],
+  "title": "The grand blog post",
+  "body": "Lorem ipsum [...]",
+  "create_at": "2014-05-03T16:55:43+02:00",
+  "updated_at": "2014-05-03T16:55:43+02:00"
+  "comments": [
     {
-      'text': 'This was really a grand blog post'
+      "text": "This was really a grand blog post",
+      "create_at": "2014-05-08T16:55:43+02:00",
+      "updated_at": "2014-05-08T16:55:43+02:00"
     },
     {
-      'text': 'I don't think it was that great'
+      "text": "I don't think it was that great",
+      "create_at": "2014-05-04T16:55:43+02:00",
+      "updated_at": "2014-05-04T16:55:43+02:00"
     }
   ]
 ```
 
-With the `map` configuration above it would take each of the objects in the comments hash and create instances of the `Comment` model from them. Then it would set the `comments` attribute of the new article and set it to the array of those comments.
+**Note**: Again this will only work if you stick with the convention. So far there is no support to configure this more fine grained.
+
+#### References
+
+While there are perfect use cases to embed documents into each other there are still plenty of use cases where referencing documents makes perfect sense. In fact this one feature where ArangoDB can really shine: Instead of just getting all referenced documents with dedicated calls to the server and without the possibility to perform any functions like filtering or sorting the data, ArangoDB can perform joins over your data just like a RDBMS.
 
-In a Rails application, they are stored in the `app/collections` directory by convention. **Note:** As of now you do have to add the `app/collections` path manually to the load path in your `config/application.rb`:
+**Note**: In the current version we're not using this power since we need to support AQL before that. As of now references are realized with dedicated calls to the database.
+
+To define references between models you just add the appropriate attributes to the `Model` classes:
 
 ```ruby
-config.autoload_paths += Dir[Rails.root.join('app', 'collections', '*.rb').to_s]
+class Author
+  include Guacamole::Model
+
+  attribute :name, String
+  attribute :posts, Array[Post]
+end
+
+class Post
+  include Guacamole::Model
+
+  attribute :title, String
+  attribute :author, Author
+end
 ```
 
-### Configuration
+As with the embedded models the real work happens in the `Collection` classes:
 
-You configure the connection to ArangoDB in the same fashion as you would configure a connection to a relational database in a Rails application: Just create a YAML file which holds the required parameters for each of your environment:
+```ruby
+class AuthorsCollection
+  include Guacamole::Collection
 
-```yaml
-development:
-  protocol: 'http'
-  host: 'localhost'
-  port: 8529
-  password: ''
-  username: ''
-  database: 'planet_express_development'
+  map do
+    referenced_by :posts
+  end
+end
+
+class PostsCollection
+  include Guacamole::Collection
+
+  map do
+    references :user
+  end
+end
+```
+
+Under the hood we will add an `author_id` to all posts holding the reference to the author. As a user this will be completely transparent for you:
+
+```ruby
+author = AuthorsCollection.by_key "23124"
+author.posts
+# => [#<Post:0x12341 …>, …]
 ```
 
-We're looking at `config/guacamole.yml` to read this configuration. If you're using Capistrano or something else make sure you change your deployment recipes accordingly to use the `guacamole.yml` and not the `database.yml`.
+The same goes for saving the data. Just add `Post`s to an `Author` as you would in plain Ruby. Passing one of the models to its `Collection` class will take care of the rest:
+
+```ruby
+author = Author.new(name: "Lauren Faust")
+author.posts << Post.new(title: "This is amazing")
+
+AuthorsCollection.save author
+# => Will save both the author and the post
+```
+
+## Integration into the Rails Ecosystem™
+
+Guacamole is a very young project. A lot of stuff is missing but still, if you want to get started with ArangoDB and are using Ruby/Rails it will give you a nice head start. Besides a long TODO list we want to hint to some points to help you integrate Guacamole with the rest of the Rails ecosystem:
+
+### Testing
+
+Currently we're not providing any testing helper, thus you need to make sure to cleanup the database yourself before each run. You can look at the [`spec/acceptance/spec_helper.rb`](https://github.com/triAGENS/guacamole/blob/master/spec/acceptance/spec_helper.rb) of Guacamole for inspiration of how to do that.
+
+For test data generation we're using the awesome [Fabrication gem](http://www.fabricationgem.org/). Again you find some usage examples in under Guacamole's own acceptance tests. We didn't tested Factory Girl yet, but it eventually will work, too.
+
+### Authentication
+
+Any integration into an authentication framework need to be done by you. At this time we have nothing to share with you about this topic.
+
+### Forms
+
+While we not tested them they should probably work due to the ActiveModel compliance. But again, this not confirmed and you need to try it out by yourself.
+
+If you give Guacamole a try, please feel free to ask us any question or give us feedback to anything on your mind. This is really crucial for us and we would be more than happy to hear back from you.
+
+## Todos
+
+While there are a lot of open issues we would like to present you a high level overview of upcoming features:
 
-**Note:** Currently we're not providing any testing helper, thus you need to make sure to cleanup the database yourself before each run. You can look at the `spec/acceptance/spec_helper.rb` of Guacamole for inspiration of how to do this.
+  * Basic AQL support for more useful queries
+  * Configuration of mapping
+  * Callbacks and dirty tracking for models
+  * An example Rails application to be used as both an acceptance test suite and a head start for Guacamole and ArangoDB
+  * An AQL query builder
 
 ## Issues or Questions