this is the initial commit with migrations working. see ./db/README.md, but basically:
1. git db:reset
2. git db:migrate

this will create an initial database and populate it

STILL TODO:

1. add the text_root, text_lemma, etc. views to the empty "views" migration
2. whatever else is needed to bring the db up to where it should b e
3. maybe add some more documentation

NOTE:

i had to hack the yaml_db gem, which is why the Gemfile line refers to my github fork
...
Merge branch 'staging' of https://github.com/quran/quran-api-rails into staging
test
trying to fix my screw up w/ big file policy and github
still fixing my bork, will not push borked in the future inshaAllah
moved rdoc README to markdown because its easier, toy with http://dillinger.io/ to experiment in formatting; you will like it for sure
ok, this is the final migration fix for sure. i should have branched off. can we start doing a branch/pull-request for code-review model for branch-merging?
added some database documentation to the main readme
fixed the saas dependency and fixed tafsir provisioning
this commit provides ES import support accounting for all of the defined mappings except tafsir (next task)
this commit provides ES import support accounting for all of the defined mappings except tafsir (next task)
adds tafsir indexing. next step: compare with mmahallawys branch and merge that in, then start working on the search controller and es settings & mappings
used text_root-ES version of app/controllers/bucket/ayat_controller.rb conflict
a working merge of text_root-ES into staging