Browse files

- removed cucumber_structure.sql from repository and added to gitignore

- updated README
- added email to travis-ci
- removed postgres user references in initial schema
- fixed fixture problems on cucumber tasks
- removed/fixed deprecated rake tasks in plugins (either non-existant or obsolete)
  • Loading branch information...
1 parent 685af63 commit 6dfaa814bfcc763fbbca7f0bfa343174066cd8f2 @aross aross committed Feb 13, 2012
@@ -3,6 +3,7 @@ log/*.log
@@ -8,3 +8,4 @@ script: "bundle exec rake spec"
+ -
@@ -10,24 +10,29 @@
### A. Dependencies
-Start by installing all the packages required by OpenCongress.
+Start by installing all the packages required by OpenCongress. The main dependencies are postgres and ImageMagick; OpenCongress will not run on mysql or sqlite. The following commands are suggestions, but ultimately you'll need to get postgres running to be able to run the app. We are currently running version of postgres 8.4.4 in production.
For Ubuntu:
sudo apt-get install postgresql postgresql-client postgresql-contrib libpq-dev ruby1.8 ruby1.8-dev rubygems libopenssl-ruby imagemagick libmagick9-dev gcj-4.4-jre
-or Mac OS X, start by installing [MacPorts](, then run:
+For Mac OS X, start by installing [MacPorts](, then run:
sudo port install postgresql84 postgresql84-doc postgresql84-server ImageMagick md5sha1sum wget
-Follow the instructions from the port install for initializing your database
+or, if you want to use [Homebrew]( (this will install version Postgres 8.4.4):
+ brew install imagemagick
+ brew install
+Follow the instructions after the packages install for initializing your database
-Then grab the gems you need:
+Install the bundle:
@@ -36,40 +41,43 @@ bundle install
-__Note for OS X:__ *You may need to specify additional compile options for the pg gem. Make sure pg_config is in PATH and run* `sudo env ARCHFLAGS="-arch x86_64" gem install pg`
+__Note for OS X:__ *You may need to specify additional compile options for your gems. Try: `ARCHFLAGS="-arch x86_64" bundle install`
### B. Database setup
-Create a postgresql install, based on the database.yml file:
+Running the following commands will create an 'opencongress' user and empty databases for the three environments (test, development, production). The migration command will populate the development database with an empty schema.
rake db:init
+rake db:migrate
-Import the tsearch2 backwards compatibility lib from wherever your postgres contribs got installed.
+### C. Data (optional)
+We are developing a process to quickly import some real legislative data. Coming soon.
- psql opencongress_development < /your/install/share/postgresql/contrib/8.4/tsearch2.sql
+### D. Starting the server
+OpenCongress uses Solr to store some data. The following command is not required, but some pages will break if Solr is not running:
-`exit` postgres user
+ rake solr:start
-### C. App Setup
+To start the webserver:
-Now you can start the solr server and run the database migrations
+ rails s
- cd ..;rake solr:start
- rake db:structure:load
- rake db:seed
-### D. Data
-create some dirs for data
+We are actively working to make the install process easier for new volunteers. Special thanks to Doug Cole for moving us along in this regard.
-Make sure all your data paths are set and exist in your environment file then run `rake update:all` to fetch and parse all available data sources. This process will take a very long time. Take a look at /lib/tasks/daily.rake for all the rake tasks if you want to run them individually.
-Now just a `script/server` and you should be running
<div class="hideme">
<hr />
-<p>Copyright (c) 2005-2010 Participatory Politics Foundation</p>
+<p>Copyright (c) 2005-2012 Participatory Politics Foundation</p>
<p>OpenCongress is licensed, as a whole, under AGPLv3. Components added prior to
OpenCongress version 3 (July 27, 2011) were and are licensed under GPLv3. All components added for or after
Oops, something went wrong.

0 comments on commit 6dfaa81

Please sign in to comment.