these modifications allow cross-development of the various forks which have drifted out of compatibility (issue #104)
config/application.rb loads config/config.yml pre-processed (switchable in config/config.yml and config/database.yml - see here for example)
added coverage/ to .gitinore (this dir exists on the tip4commit fork)
added caveat to README.md indicating that phantomjs is a testing pre-req
NOTES:
pre-processing config.yml is inconsequential if config.yml contains no erb - i added this to allow peer4commit and tip4commit to co-exist functionally in the same repo - without this functionality, the config.yml would either need to be commited to the repo or manually restored upon each branch change - so i figured this was the least intrusive option
allow peer4commit and tip4commit to co-exist functionally in the same repo - without this functionality one would need to manually swap config files when switching forks
im not sure why the schema was modified - this was not my doing - there must had been some manual additions to the migration files after the initial migrations (notably the email index in the users table)
the addition to .gitignore is o/c also inconsequential - it merely allows peer4commit and tip4commit to co-exist functionally in the same repo
CHANGES:
NOTES: pre-processing config.yml is inconsequential if config.yml contains no erb - i added this to allow peer4commit and tip4commit to co-exist functionally in the same repo - without this functionality, the config.yml would either need to be commited to the repo or manually restored upon each branch change - so i figured this was the least intrusive option
allow peer4commit and tip4commit to co-exist functionally in the same repo - without this functionality one would need to manually swap config files when switching forks
im not sure why the schema was modified - this was not my doing - there must had been some manual additions to the migration files after the initial migrations (notably the email index in the users table)
the addition to .gitignore is o/c also inconsequential - it merely allows peer4commit and tip4commit to co-exist functionally in the same repo
this is the equivelant for this repo of a similar commit to the tip4commit fork