- Fork the repo
- Install VirtualBox
- Install Vagrant
- Request access to Okta Preview from TechOps
$ cd vagrant_postgres91_utf8_rails$ vagrant up- vagrant up will provision the Vagrant box, create the databases, and run the bundler
$ vagrant ssh$ cd workspace
$ echo "PORT=9292" > .env$ echo "RACK_ENV=development" >> .env$ rake db:schema:load- loads the latest schema without going through each migration individually (faster than rake db:migrate)
$ rake db:seed- add dummy data to local environment
$ RAILS_ENV=test rake db:schema:load- set up test environment
- Using capybara-webkit
$ xvfb-run rspec- If you repeatedly receive the error "Xvfb failed to start," try
$ xvfb-run --server-num=1 rspec.
- Using poltergeist
$ bundle exec rspec
- For manual testing, see the db/seeds.rb file for user log-on information
$ foreman start(this will not return)
If your foreman is very slow, try getting a new network setup:
$ sudo dhclient(this will give a File Exists, that's ok)$ foreman start
View the dev site locally:
When deploying to a new heroku instance (developers will NOT need to do this), please specify e-mail account settings in the following configuration variables.
Account details for sending emails from:
MAIL_SERVER=smtp.gmail.comMAIL_PORT=587MAIL_DOMAIN=thoughtworks.orgMAIL_USERNAME=do-not-reply@thoughtworks.orgMAIL_PASSWORD=<password>MAIL_TLS=true
The Address that should appear in the "from" line of the sent e-mails:
MAIL_FULL_EMAIL="TW ReviewSite <do-not-reply@thoughtworks.org>"
The base domain that should be used for the links that appear in the emails.
DOMAIN=twreviewsite.herokuapp.com
In order to prevent the mailer from sending e-mail on non-production heroku instance, it is possible to redirect all e-mail to an address that you control.
EMAIL_OVERRIDE=someone@somewhere.com
Email Valerie Roske (varoske@thoughtworks)
