Contents

cide - Continuous Integration Docker Environment
================================================

`cide` makes it easy to reproduce CI builds on the developer computer by
providing the same docker environment.

Run `cide` in the project root to run a build. Configure by providing a
`.cide.yml` file.

Usage
-----

Just run `cide` inside of your project. cide will look for a .cide.yml file
for configuration but all arguments are also passable trough command-line
arguments. If a Dockerfile already exists it will be used instead.

Example
-------

`.cide.yml`
```
---
image: "ruby:2.1"
as_root:
- apt-get update -qy && apt-get install -qy libxml2-dev
command: bundle && bundle exec rspec
```

Features
--------

* straighforward to use, just run `cide` inside of your project
* works on OSX with boot2docker
* integrates easily with jenkins or other CI systems

Limitations
-----------

A temporary Dockerfile has to be created in the project's root because docker
doesn't allow referencing files outside of the directory (even with a symlink)

TODO
----

* linked container
* schema validation
* use the /cache volume
* multi-container runs
* `cide setup` to configure inside of a project
* `cide gc` to cleanup old cide builds
* travis.yml compatiblity with docker containers that map to languages
* add ways of exporting artifacts
* ENV GEM_HOME is container specific

Version data entries

1 entries across 1 versions & 1 rubygems

Version	Path
cide-0.0.2	README.md