Home cooked food delivered/pickup for busy people

• Product Owner: Dan Sajjad
• Scrum Master: Shinji Furuya
• Development Team Members: Andrew Fung, Alex Wong

1. Usage
2. Requirements
3. Development
   1. Installing Dependencies
   2. Tasks
4. Team
5. Contributing

Initial Postgres Database Setup

• If you don't have Postgres.app, point to http://postgresapp.com/, download, and install the app
• Open Postgres.app from your Applications folder
• Click on the Postgres elephant icon on the menu bar and select 'Open psql' to start the Postgres instance (a psql terminal window should open up)
• In the window, create the database table by typing:

CREATE DATABASE mwl_db;

###Elastic search

• Download elasticsearch zip (https://www.elastic.co/downloads/elasticsearch)
• Unzip the file
• Copy elasticsearch.yml file from mwl root folder into the config folder of the unzipped file
• To start elasticsearch, in the terminal, go to the root folder of the unzipped file and type:

./bin/elasticsearch & hit enter

• This will start elastic search on localhost:9200

####Seed elastic search for meals generated by chefs

• From your application folder, copy "meals.json" file
• Go to the root folder of the unzipped elasticsearch file
• Paste the copied file into the folder
• To drop the data run the following command from anywhere in the terminal:

curl -XDELETE 'http://localhost:9200/_all'

• In the terminal, from inside the elasticsearch folder run the following command:

curl -XPOST 'localhost:9200/mwl/meal/_bulk?pretty' --data-binary "@meals.json";

• Node 0.10.x
• Express
• Elasticsearch 2.3.x
• Postgresql 9.1.x

The production application version was deployed to AWS with a multiple EC2 container set-up. For development, Docker containers separately encapsulated the Postgres database and the server/client processes. The containers were boostrapped and linked together using a docker-compose yaml file, with the necessary port exposures and environment settings to allow communication between the running containers. Elasticsearch was initially considered as another container, but due to the nature of both the client and the server making calls to Elasticsearch, it was not feasible to control the client environment for production purposes, thus switching to the AWS Elasticsearch service instead.

From within the root directory:

sudo npm install -g bower
npm install
bower install

###Starting the application

• From project root folder

npm start
npm run watch

- To start ElasticSearch db: from elasticsearch's unzipped folder
```sh
./bin/elasticsearch

• To start postgres: run Postgres application
• Install Postgres globally

npm install -g pg
npm install -g sequelize sequelize-cli

• Creating tables with seed data

sequelize model:create --name users --force --attributes firstName:string,lastName:string,email:string,description:string,phone:string,password:string,address:string,zip:string,profile:string,chef:boolean,numOrders:integer,avgRating:float,stripe:string

sequelize model:create --name orders --force --attributes userId:integer,chefId:integer,mealId:string,food:string,cuisine:string,description:string,quantity:integer,price:float,userAddress:string,orderDate:date,rating:float,review:string,image:string,delivered:boolean

sequelize db:migrate

sequelize db:seed:all

• With everything running visit your localhost:3000 to view the application

View the project roadmap here

See CONTRIBUTING.md for contribution guidelines.