Known Panda Dependencies

panda.md

Known Panda Dependencies

Background:

• All directions assume each app passes a health_check
• All projects should be using their correct ruby version
• All projects should run against master or develop to test Panda
• dropdb [site]_dev will fail if delayed_job is running for that app
• dropdb [site]_dev will fail if pow/rails is running against that app

Order of Configuration

Pumpkin

• psql pumpkin_dev
• SELECT * from pricing_plans; // confirm plans exist
• if no plans exist run bundle exec rake db:setup

Holmes

Holmes bin/setup is broken. It supposes there exist csv files to seed correct data. Instead we must use a db scrub.

• Open Slack/#ext-infogain and download holmes_scrub.dump.zip
• Unzip scrub data to [holmes]/db/holmes_scrubbed-2017-09-21.dump
• $ cd to [holmes]
• Run all the following commands to import the dump:

createdb holmes_dev
createuser holmes
createuser scrub
createuser projectdx
createuser holmes-owner
createuser etl_user
createuser bi_manager
createuser readonly_user
createuser dw_stage_ro
createuser cloveretl_reporting
createuser axiomatics_ro
pg_restore -U postgres -d holmes_dev -1 db/holmes_scrubbed-2017-09-21.dump
bundle exec rake db:bootstrap

Nemo

Nemo uses Holmes data for Contractor and User data. Holmes must be fully bootstrapped before we setup Nemo.

• dropdb nemo_dev && dropdb nemo_test
• bin/setup // this will extract data from Holmes and populate contractor tables/caches

Supporting Delayed:Jobs

• Open (unicorn piranha lenny nemo holmes tiro nightingale) in separate tabs
• In each tab execute bin/delayed_job start

Panda

Panda requires bumbleworks AND delayed_job to handle tasks

• script/delayed_job start
• bundle exec rake bumbleworks:flush_storage (run optionally to delete all existing cached items)
• bundle exec rake bumbleworks:bootstrap bumbleworks:start_worker -v
• rails s // unless you have pow booting for you

You are now ready to open http://panda.dev