To get started, install all the required software first and then follow the instructions to set up each software step-by-step. If you have any problems during the set up, refer to the Common Set Up Problems & Solutions section towards the end of the document.
####Required Software
- Git Client
- Node.js
- Visual Studio 2013
- IIS Manager
####Cloning the Predator Repository
- Open Git Bash or preferred git utility.
- Right-click your Desktop, and select Git Bash Here. This will open the Git command prompt from your Desktop's directory.
- Clone the Predator repo from GitHub in your local machine.
git clone https://github.com/JSamp701/Predator-Check-Management-System.git
- Enter in your Git-hub use name and password.
####How to Set Up Node.js *****these instructions need to be checkededited
- Open Node.js Command Prompt.
- Navigate inside the app folder (i.e.
cd C:\Users\fwhatley\Desktop\Predator\Predator.App\app
) - Run the commands below in order.
npm install -g grunt-cli
npm install
which will bring in all the dependenciesgrunt dev
which will- process .styl files down to the site.css file required to run the site
- watch your files and provide livereload
- kick off a local web server http://localhost:3000
####How to Set Up Visual Studio 2013
Opening the Predator project
- Open Visual Studio 2013.
- Open the Predator project located inside Predator folder by going to menu FILE > Open > Project/Solution and selecting Predator.sln.
Setting Up the Web API Project Properties
- Once the solution is opened to set up the Web API project, select the Predator.Api project in the Solution Explorer section.
- Right click on the project and select properties.
- In the properties window, select the Web tab and select
- Start Action: "Don't open a page. Wait for request from an external application."
- Servers: Local IIS
- Once the two options are selected, click "Create Virtual Directory".
- Hit Ctrl + S to save all the changes and Ctrl + F4 to close the properties window.
Setting Up the Solution Properties
- In the Solution Explorer section, right click on the solution and choose properties.
- In the properties window on the left panel, go to Common Properties > Startup Project.
- On the right panel, choose "Single startup project" and select "Predator.Api" and click OK to close the window.
Testing Predator.Api with Swagger
Navigate to this address to open swagger to test the endpoints. http://localhost/Predator.Api/swagger
####How to Set Up IIS Setting Up Predator.Api
- Open IIS 7 Manager.
- Enable Anonymous Authentication (for OPTIONS API request, authorization for OPTIONS is set in web.config).
- Enable Windows Authentication.
Setting Up Predator.App
- Enable Anonymous Authentication because the first call this app makes is to get the current user information from the API which requires authentication. We do this so that the user doesn't have to authenticate twice.
- How to enable IIS Management Console in Windows 7
- How to fix: Handler “PageHandlerFactory-Integrated” has a bad module “ManagedPipelineHandler” in its module list
- ASP.NET IIS 7.5 HTTP 500.21 error
- IIS - this configuration section cannot be used at this path (configuration locking?)
- How can I enable assembly binding logging
- In IIS, why doesn't Window Authentication show up as one of the options for my web application?
- IIS Server
- Microsoft .NET 4.5 Framework
- Open a terminal and navigate to Predator.App folder.
- Run
grunt prod
which will run tasks to optimize and minify the front-end. The server ready files will be placed under the folder dist. - Use an FTP or SSH client to upload the contents of dist to the server.
- Navigate to Predator.Api folder.
- Open and FTP or SSH client and upload the contents Predator.Api to the server.
- Merge all branches to
master
. - After the merge is complete, tag and push
master
.git tag PD4
(change PD4 to your release version)git push origin master --tag