-
Notifications
You must be signed in to change notification settings - Fork 0
Installation Instructions for Ubuntu 12.04 Precise
You need bundler 1.2 or higher in order to successfully run bundle install
$ bundle install
# Fill in `config/dblogin.yml`
$ rake db:create
$ rake db:schema:load
To setup some example data: $ rake db:seed $ rake db:seed
bundle install
will likely fail as some of the gems require native libraries to be installed on your system. The following gems require libraries which are not included on Ubuntu 12.04 by default:
- Ruby >= 1.9 compiled with
psych
,readline
,zlib
andopenssl
- nokogiri
sudo apt-get install libxslt1-dev libxml2-dev
- capybara-webkit
sudo apt-get install libqt4-dev libqtwebkit-dev g++
- pg
sudo apt-get install libpq-dev
- sqlite3
sudo apt-get install sqlite3 libsqlite3-dev
- memcached
- sudo apt-get install memcached libsasl2-2
One-liner for the brave:
sudo apt-get install libxslt1-dev libxml2-dev libqt4-dev libqtwebkit-dev g++ libpq-dev sqlite3 libsqlite3-dev memcached libsasl2-2
We use the Searchify heroku addon to power the search index for honolulu answers. In order to use this in development you can either run a copy of Indextank (which is what Searchify is built on) or add the searchify addon to a heroku app, and copy the provided search api endpoint to your .env file.
Since Searchify only offer paid plans, for development you might want to check out the following free IndexTank providors and use the API key they supply: (1) HoundSleuth (2) IndexDen
We use Big Huge Thesaurus in order to enhance search queries. In order to run this in development you will need an API key, freely available at bht.com.
Honolulu Answers uses Environment variables for configuration. It expects a BHT_API_KEY
, and SEARCHIFY_API_URL
to be set to the searchify endpoint (which can be retrived from heroku config
once searchify is an addon for your app)
foreman
is a great tool for checking your Procfile used for heroku, and running your application locally. When running foreman start
this will load enivronment variables from .env
if that file is found.
Included in this project is an example of what the .env
file should include. In order to use this make a copy and replace the values appropriate values for your setup.
$ cp .env.sample .env
Now edit .env
to set the correct url to the searchify endpoint.
Also included config/dblogin.yml.sample
copy this file too
$ cp config/dblogin.yml.sample config/dblogin.yml
Now if you need to set login credentials for your database that that are different then the default, you can do it in config/dblogin.yml
Both config/dblogin.yml
and .env
are added to the .gitignore
so changes should not be committed, dont commit passwords :)