• Summary
• Prerequisites
• Features
• Subprojects
  • UI
  • Database
  • Pathfinding Algorithm
  • Server/AWS
• Testing
• Credits

Please click the image below:

All you need to run TunnelRaider is an internet connection and a device, preferably a mobile device, with which to navigate.

Please click the image below:

The server side of the app is divided into two parts:

• The app server, which serves the app and GUI info to the client and has instructions on how to use the pathfinding server.
• The pathfinding server, which takes requests from the client and serves as an interface to the dataase in order to find the path requested.

To start the react server, two options are available. To start the react scripts listening on the default port (3000, if availiable), run the command npm start. If you want to start the react scripts listening on port 80, run the command npm run start80 as root.

• Start before the client.
• Run by executing npm run start-server in the repo root directory. To use a local database with the server, run the command npm run start-server-local instead.
• Using https://github.com/mysqljs/mysql to access the database.
• Using https://github.com/expressjs/express to run the server.

Use the CloudFormation template AWS-Ububtu.yml to create the stack. Once the stack has been created, log into its EC2 server and run the command sudo bash /var/lib/cloud/instances/*/user-data.txt <BRANCH>, where <BRANCH> is whatever branch from the repository you want the server to use. If no branch is specified, the script will default to the master branch. After the command finishes (it might take awhile), both the app server and the navigation server should be up and running. If they aren't, logs can be found in ~/repo/app.log and ~/repo/server.log.

The User Interface was designed to feel both familiar and functional. The design pulls its inspiration from many common mobile applications. It has a static header and footer with dynamic content in the middle. Additional content is brought into view by means of two side loading menus.

Design Inspiration

Team Credits

The pathfinding algorithm uses a modified implementation of the A* algorithm that allows for navigation to multiple end points. For an explanation of the standard A* algorithm, please click the image below:

Credit for the above video goes to Sebastian Lague, please subscribe: https://www.youtube.com/channel/UCmtyQOKKmrMVaKuRXz02jbQ

• Start before the client.
• Run by executing npm run start-server in the repo root directory. To use a local database with the server, run the command npm run start-server-local instead.
• Using https://github.com/mysqljs/mysql to access the database.
• Using https://github.com/expressjs/express to run the server.

Use the CloudFormation template AWS-Ububtu.yml to create the stack. Once the stack has been created, log into its EC2 server and run the command sudo bash /var/lib/cloud/instances/*/user-data.txt <BRANCH>, where <BRANCH> is whatever branch from the repository you want the server to use. If no branch is specified, the script will default to the master branch. After the command finishes (it might take awhile), both the app server and the navigation server should be up and running. If they aren't, logs can be found in ~/repo/app.log and ~/repo/server.log.

Beta Testers included members of the Wright State University Computing and Telecommunications Services office, as well as members of the Wright State Student Body and members of the Fairborn/Beavercreek Community.

Validation of CloudFormation templates is done by running the command:

$ aws cloudformation validate-template --template-body file://./TEMPLATE.yml

Where TEMPLATE.yml is the local filename of the template.

An example using AWS-Ubuntu.yml:

$ aws cloudformation validate-template --template-body file://./AWS-Ubuntu.yml
WSU CS-3900 Server Template: This template creates a server to be used by the Spring 2019 CS-3900 project.
  The template automatcally sets up a EC2 server and peripherals, with a bash script for setup appearing in a file
  matching the pattern /var/lib/cloud/instances/*/user-data.txt. To setup the server, run the command
  "sudo bash /var/lib/cloud/instances/*/user-data.txt <BRANCH>", where <BRANCH> is the name of the branch from the git
  repository that the server should use.  The setup script will then run the start.bash file in that branch.
PARAMETERS		Name of an existing EC2 KeyPair to enable SSH access to the instance	False	KeyName
PARAMETERS	0.0.0.0/0	 The IP address range that can be used to access the EC2 instance	False	SSHLocation
PARAMETERS	t2.micro	WebServer EC2 instance type	False	InstanceType

To view detailed information on all resources that AWS CloudFormation will create first create a change set:

$ aws cloudformation create-change-set --stack-name testing --change-set-name changes --change-set-type CREATE --template-body file://./AWS-UbuntuRDS.yml

Then to view those changes run:

$ aws cloudformation describe-change-set --change-set-name changes --stack-name testing

When done, clean up by running:

$ aws cloudformation delete-change-set --change-set-name changes --stack-name testing
$ aws cloudformation delete-stack --stack-name testing

Testing of the pathfinding is done by running npm test command in the server directory.

• Jared Cole
• Matt Eilerman
• Eric Foy
• Ryan Ley
• Hayden Mankin
• Matt Masten
• Owen O'Connor
• Ryan Slater

• Michelle Cheatham
• Matt Kijowski

• Wright State University and the Wright State University Marketing Department
• David Kendrick
• Thank you to all who tested TunnelRaider for us!