This repository has been archived by the owner. It is now read-only.
(DEPRECATED) Work towards a bootstrap for getting a full eRegs dev environment set up.
Clone or download
Pull request Compare This branch is 28 commits ahead of micahsaul:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.


eRegulations is a web-based tool that makes regulations easier to find, read and understand with features such as inline official interpretations, highlighted defined terms, and a revision comparison view.

eRegs is made up of several core components for parsing and serving regulations:



Regulation Content:

The following diagram should give a rough idea of what the relationships between these repositories are in the CFPB eRegs workflow.

eRegulations Repositories/Components

This repository contains scripts that boostrap a coherent eRegulations working environment, either locally or in a Vagrant virtual machine.

Bootstrap Locally

To bootstrap a local (i.e. not virtualized) eRegs environment, you'll need to install Python's virtualenv and virtualenvwrapper, as well as Node's Version Management.


Python virtualenv

Install virtualenv:

pip install virtualenv

Then install and configure virtualenvwrapper. More information on how virtualenvwrapper works and how you may wish to set it up in your shell can be found in the virtualenvwrapper documentation.

pip install virtualenvwrapper
export WORKON_HOME=~/envs
mkdir -p $WORKON_HOME
source `which`

Node dependencies (nvm, grunt)

Install nvm using nvm's install script.

The nvm nvm gives more detail about how to use nvm. For now, you can simply run the following (and add them to your shell's profile or run commands file):

export NVM_DIR="$HOME/.nvm"
source $NVM_DIR/

regulations-site requires Node 4, grunt, and browserify, so use nvm to install and use Node, and then install the later two using npm:

nvm install 4
nvm use 4
npm install -g grunt-cli browserify


Once you have these requirements installed you can run the


This will clone all of the eRegs repositories, make seperate virtualenvs for them, and setup their dependencies.

You also have the option of only bootstrapping specific components of eRegulations. For example:

./ -b core -b site

This will bootstrap just the API (core) and the site, without the parser. This would be useful for serving regulations that have already been parsed (which then just need to be added to the API). takes the following arguments:

  • -v, verbose output. The output of all commands will be provided regardless of success or failure
  • -d, set Django debug flags to true in regulations-core and regulations-site.
  • -c [URL], API url to configure for regulations-parser and regulations-site
  • -b [...] component to bootstrap, either parser, core, or site. This can be provided up to three times.

Bootstrap with Vagrant

To bootstrap eRegs in a Vagrant virtual machine, you'll need to install Vagrant locally. Everything else should be taken care of by this repository's Vagrantfile.


Install Vagrant. On Mac OS X, this can be done with Homebrew:

brew install vagrant


The eRegs bootstrapping process will be performed as part of the Vagrant provisioning process. All one needs to do is provision the Vagrant virtual machine.

vagrant up

Once the virtual machine is running, you should be able to access regulations-core at http://localhost:8000 and regulations-site at http://localhost:8001.

You can also connect to the virtual machine via SSH.

vagrant ssh


Before you can use regulations-site to browse any regulations, you'll need to parse some with regulations-parser. To do this you'll need to SSH into the virtual machine and run the parser.

To parse the CFPB's Regulation D, from eCFR, for example, you would do the following:

workon regparser
cd /vagrant/regulations-xml-parser
./ ecfr 12 ../fr-notices/annual/CFR-2012-title12-vol8-part1004.xml
./ json 12 1004

This will put eRegs JSON for Regulation D in regulations-stub/stub. You can load that JSON into the API using regulation-stub's script or regulation-core's import_reg command.

cd /vagrant/regulations-stub
./ -a http://localhost:8000/ -r 1004

Once completed, the JSON for this regulation can be browsed in regulations-core at http://localhost:8000 and can be viewed in regulations-site at http://localhost:8001.

For more information on parsing regulations, please see the regulations-xml-parser README

Because all of the components are stored in your Vagrant project directory you can use your favorite IDE or editor to work on them and see your changes running in the virtual machine.