Public | Automated Build

Last pushed: a year ago
Short Description
ticket-driver
Full Description

Ticket Driver

A unified shopping experience that includes:

  • Event ticket sales
  • VIP table reservation sales for nightlife / day life
  • VIP table reservation contact forms for nightlife / day life
  • Guest list signup forms for nightlife / day life
  • OpenTable Partner API reservation booking forms for restaurants
  • Upselling designed into the purchase experience
  • Cross selling to nearby venues designed into purchase experience
  • Deep integration with Marketo for personalized cross selling and upselling based on anonymous behavior tracking and past transaction history
  • Enhanced transaction customer experience features, like special offers to share information on social media
  • Live-chat connection to the call center operators when appropriate

Continuous Delivery

This project uses Continous Delivery through CodeShip, and will automatically
deploy any commit merged into the master or staging branches if all tests pass.

Merge into staging to deploy to staging.ticketdriver.com

Testing services

This project is set up at:

Development mode

This project uses Docker for complete parity between development, test, staging,
and production environments. To spin up a development environment, you
first need Docker. We use the new Docker for Mac and we love it.

Spin up your local development environment

To run Ticket Driver in a local development environment, simply switch to the project folder in a Terminal and tell it:

docker-compose up

That will fetch the required source containers, build this project's custom containers, and spin up a local development environment that consists of a web server container called web and a database server container called db.

Run commands

Use docker-compose run web to run commands in the web container.

For example, run something like this from the command line:

docker-compose run web bundle exec rake -T

That tells Docker Compose to run rake -T inside of the web container.

Testing

Prepare your test database first with:

docker-compose run web bundle exec rake db:migrate
docker-compose run web bundle exec rake db:test:prepare

Run RSpec tests

This project uses RSpec for unit tests. Run them with:

docker-compose run web bundle exec rake spec

This will also generate a coverage report in coverage/index.html that you
can access from port 3001.

Run Cucumber features.

This project uses Cucumber for behavior specs. Run them with:

docker-compose run web bundle exec cucumber

This will also generate a coverage report in coverage/index.html that you
can access from port 3001.

Rebuilding your containers

Generally you won't need to do this often. But if you ever need to change the
Gemfile in the project then you can rebuild the web container with:

docker-compose build web
Docker Pull Command
Owner
hkwebnerds
Source Repository