This is the source that becomes [immutant.org](http://immutant.org/). 

## Building It

You'll need ruby 1.8.7 or greater and the [awestruct gem](http://awestruct.org/). 
The easiest way to get awestruct and its dependencies is to use [bundler](http://gembundler.com):

    ~/immutant.org $ gem install bundler
    ~/immutant.org $ bundle install
    
Then run awestruct in development mode:

    ~/immutant.org $ bundle exec awestruct -d

This will generate the static site into `_site` and serve it on [http://localhost:4242/](http://localhost:4242/)

Most of the changes you make to the source files should be noticed immediately
and trigger the proper regenerations. Some changes may not get picked up - in that
case, you'll need to stop awestruct, `rm -rf _site`, and restart awestruct.


This is the source that becomes [immutant.org](http://immutant.org/). 

## Building It

You'll need ruby 1.8.7 or greater and the [awestruct gem](http://awestruct.org/). 
The easiest way to get awestruct and its dependencies is to use [bundler](http://gembundler.com):

    ~/immutant.org $ gem install bundler
    ~/immutant.org $ bundle install
    
Then run awestruct in development mode:

    ~/immutant.org $ bundle exec awestruct -d

This will generate the static site into `_site` and serve it on [http://localhost:4242/](http://localhost:4242/)

Most of the changes you make to the source files should be noticed immediately
and trigger the proper regenerations. Some changes may not get picked up - in that
case, you'll need to stop awestruct, `rm -rf _site`, and restart awestruct.

## Deploying It

We use CI to build and deploy. 

Pushing to master should generate a staging build that pushes to:
<staging.immutant.org>.

To have CI generate the live site, push to the production branch:
    
    git push origin master:production

Update the readme w/production build instructions.
Update the readme w/production build instructions.
