Bundler groups » History » Revision 2
Revision 1 (Ohad Levy, 06/19/2012 03:04 AM) → Revision 2/3 (Ohad Levy, 06/19/2012 03:18 PM)
h1. Bundler groups
First of all, if you installed foreman via a package (rpm, deb) you should not care much about bundler and bundler groups, however feel free to stick around.
Since foreman upgraded to rails 3.x, we also moved to using "Bunder":http://gembundler.com/.
In order not to force all users to install all possible library stacks (e.g. if you don't care about provisioning, you don't really need the code which handles EC2), we've have broken down the gem list into groups.
h1. How to exclude groups from bundler
<pre>
bundle install --without group1 group2 group3
</pre>
you can also review/edit .bundle/config file instead.
the current groups break down more or less into to main categories:
h2. Database
we currently support *sqlite*, *mysql* and postgres* databases, and since you only need one of those, you need to tell bundler not to install all of the rest
So assuming you want to use postgres, simply run:
<pre>
bundle install --without sqlite mysql mysql2 ...
</pre>
h3. MySQL
Rails supports two different 'drivers' to communicate with a MySQL server (or servers), mysql gem normally works, but people had great results with mysql2 and it seems to be more maintained these days.
h2. Compute Resource related groups
h3. EC2
requires the *fog* group
h3. oVirt / Libvirt
requires the *fog* and *ovirt* groups
h3. Libvirt
requires the *fog* and *libvirt* groups
h3. VMWare
requires the *fog* and *vmware* groups
h2. Development / Test groups
requires *test* and *development* groups.
note that if you are using the rails console, its also recommended to use the console group for better text formatting / helpers etc.