CF example app: ping-pong matching server

This is an app to match ping-pong players with each other. It's currently an API only, so you have to use curl to interact with it.

It has an acceptance test suite you might like to look at.

Note: We highly recommend that you use the latest versions of any software required by this sample application.

Running on Pivotal Web Services

Log in.

cf login -a https://api.run.pivotal.io

Target your org / space. An empty space is recommended, to avoid naming collisions.

cf target -o myorg -s myspace

Sign up for a cleardb instance.

cf create-service cleardb spark mysql

Push the app. Its manifest assumes you called your ClearDB instance 'mysql'.

cf push -n mysubdomain

Export the test host

export HOST=http://mysubdomain.cfapps.io

Now follow the interaction instructions.

Running locally

The following assumes you have a working, recent version of Go installed, and you have a properly set-up Go workspace.

The minimum required set-up for a Go workspace is a directory structured as shown below:

|-<Go-workspace-name>
	|-src
	|-bin
	|-pkg

Also, ensure that you set your GOPATH environment variable using your workspace name: export GOPATH=$HOME/.../<Go-workspace-name>.

1. Install and start MySQL:

   brew install mysql
   mysql.server start
   mysql -u root

2. Create a database user and table in the MySQL REPL you just opened:

   CREATE USER 'gopong'@'localhost' IDENTIFIED BY 'gopong';
   CREATE DATABASE pong_matcher_go_development;
   GRANT ALL ON pong_matcher_go_development.* TO 'gopong'@'localhost';
   exit

3. Install and start the application server:

   go get github.com/cloudfoundry-samples/pong_matcher_go
   cd $GOPATH/src/github.com/cloudfoundry-samples/pong_matcher_go
   go install
   $GOPATH/bin/pong_matcher_go

4. Export the test host in another shell, where you can then run the interactions:

export HOST=http://localhost:3000

Now follow the interaction instructions.

Interaction instructions

Start by clearing the database from any previous tests. You should get a 200.

curl -v -X DELETE $HOST/all

Then request a match, providing both a request ID and player ID. Again, you should get a 200.

curl -v -H "Content-Type: application/json" -X PUT $HOST/match_requests/firstrequest -d '{"player": "andrew"}'

Now pretend to be someone else requesting a match:

curl -v -H "Content-Type: application/json" -X PUT $HOST/match_requests/secondrequest -d '{"player": "navratilova"}'

Let's check on the status of our first match request:

curl -v -X GET $HOST/match_requests/firstrequest

The bottom of the output should show you the match_id. You'll need this in the next step.

Now pretend that you've got back to your desk and need to enter the result:

curl -v -H "Content-Type: application/json" -X POST $HOST/results -d '
{
    "match_id":"thematchidyoureceived",
    "winner":"andrew",
    "loser":"navratilova"
}'

You should get a 201 Created response.

Future requests with different player IDs should not cause a match with someone who has already played. The program is not yet useful enough to allow pairs who've already played to play again.