Installing Integral

Integral is written in <a href="http://ruby-lang.org">Ruby</a>, and depends on a couple of <a href="http://www.rubygems.org">Ruby gems</a>, so you’ll need to install Ruby and rubygems before you go any further. Once they’re setup this command should install all the gems that you need: $ sudo gem install rake thor activerecord rspec Integral stores it’s data in a relational database. You can use any database that is supported by ActiveRecord. In this example we’ll use <a href="http://www.sqlite.org">SQLite</a>, which is very easy to get started with as the Integral config files are pre-configured for it. You’ll need to install your database, then ensure that Ruby support for your database is installed. In the case of SQLite that means you need the sqlite3-ruby gem: $ sudo gem install sqlite3-ruby Grab yourself a copy of the Integral source code. You can download a tarball from Github, or clone the repository directly with git: $ git clone git://github.com/gma/integral.git $ cd integral Once you’ve got the code you need to tell Integral how to connect to your database (the database.yml file is in the same format as used by <a href="http://www.rubyonrails.org">Ruby on Rails</a>, so you can follow <a href="http://wiki.rubyonrails.org/rails/pages/database.yml">instructions elsewhere</a> on how to configure it): $ cp config/database.yml.sample config/database.yml You also need to make a copy of the default Integral configuration file. $ cp config/config.yml.sample config/config.yml If you want to use a different database just edit the database.yml file accordingly. MySQL and Postgres users will now need to create their databases (called integral_test and integral_production – note that there is no separate development database as there is with <a href="http://www.rubyonrails.org">Ruby on Rails</a>). SQLite users can skip the creation step (it happens automatically) and move straight on to setting up the database schema. We need to do it twice so we can run the tests in the test database whilst storing our real data in the production database: $ INTEGRAL_ENV=test thor db:migrate $ thor db:migrate <a href="http://yehudakatz.com/2008/05/12/by-thors-hammer/">Thor</a> is a very neat library that makes it extremely easy to write binary commands in Ruby – it is used for all the command line scripting in Integral. Finally, to check that everything is working, try running Integral’s tests (there should be no failures): $ rake spec Now list the available thor tasks to check that thor is working okay: <pre> $ thor -T db -- db:migrate migrate the database db:init create first successful test run app --- app:list show all applications app:add NAME PATH add an application to be tested app:remove NAME remove an application (caution!) app:activate NAME activate an existing application app:deactivate NAME deactivate an active application tests ----- tests:run run the integration tests tests:recent show results of last 5 runs versions -------- versions:staging [--verbose] show apps on test server versions:live [--verbose] show apps on live server versions:check APP VERSION [--verbose] check whether combination is tested </pre> You’re done. Time to configure your applications – head over to [[Configuring Integral]]. 2008-11-11T13:50:32-08:00 79486 installing-integral

72328

Installing Integral

2009-03-03T07:14:29-08:00

2122