Skip to content
Burger devouring app
JavaScript HTML Other
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
GCP
Instructions
config
controllers
db
models
public
views
.1.gitignore
.DS_Store
.gcloudignore
.gitattributes
.gitignore
README.md
app.yaml
gcp.sh
gcpDeploy.sh
gcpRun.sh
herokuCreate.sh
herokuPush.sh
package-lock.json
package.json
server.js

README.md

Burger Log - Node Express Handlebars / Google Cloud Platform

Overview

Burger Log

This application is a burger logger using MySQL, Node, Express, Handlebars and a homemade ORM. It uses the MVC design pattern, Node and MySQL to query and route data in your app, and Handlebars to generate your HTML. I also use some client side renderring per the advice of an instructor (Sterling) to deal with Modal Dialog boxes and quick changes to HTML.

Note

I deployed to Google Cloud Platform (not Heroku) since I already reached my limit on Heroku apps. I have outlined the steps for deploying app and DB to GCP. It is much more involved than Heroku but provides some benefits in access and scale.

Links

Technologies Used

  • HTML/CSS/Javascript/JQuery/Bootstrap
  • SQL, mySQL and Google Cloud Platform (App Engine, SQL DB, SQL Admin Services)
  • Handlebars, Node.js, Express, Path

Screenshots

Burger Log

Design

  • Burger Log is a restaurant app that lets users input the names of burgers they'd like to eat.

  • Whenever a user submits a burger's name, the app displays the burger on the left side of the page -- waiting to be devoured.

  • Each burger in the waiting area also has a Devour it! button. When the user clicks it, the burger will move to the right side of the page.

  • The app stores every burger in a mySQL database, whether devoured or not.

  • The user can also delete a devoured burger by clicking the delete (X) icon to the right of devoured burger.

  • I used ES6 classes for all the classes/objects (e.g. Orm, Connection etc)

  • Follows Model View Controller (MVC) pattern

Directory structure

The major files and directories from the look like the following structure:

.
├── config
│   ├── Connection.js
│   └── Orm.js
│
├── controllers
│   └── burgers_controller.js
│
├── db
│   ├── schema.sql
│   └── seeds.sql
│
├── models
│   └── burger.js
│
├── node_modules
│
├── package.json
│
├── public
│   └── assets
│       ├── css
│       │   └── burger_style.css
│       └── img
│           └── burger.png
│
├── server.js
│
└── views
    ├── index.handlebars
    └── layouts
        └── main.handlebars

Hosting on Google Cloud Platform

I deployed to Google Cloud Platform (not Heroku) since I already reached my limit on Heroku apps. I have outlined the steps for deploying app and DB to GCP. It is much more involved than Heroku but provides some benefits in access and scale.


You can’t perform that action at this time.