Day 31: Deployment

Wednesday, July 13, 2016

Topics

Deploying a Node App to Heroku

• Heroku - Cloud platform/infrastructure as a service
• Heroku Toolbest - Command-line tools for Heroku
• Getting Started on Heroku with Node.js
• Setting Config Vars on Heroku

Deploying an Angular App to GitHub Pages

• The contents of the app directory must be at the top level of your gh-pages branch.
• The bower_components directory must be in the repository, unless you are not dependent on it (if, for example, you’ve concatenated all of your third-party JS and CSS files).
• Any compiled/transpiled files (e.g. bundle.js) must be in the repository.

Projects

Meganote Server updates

• Add ESLint config and fix issues.
• Add a helpers directory.
• Get port number from ENV.
• Do not load dotEnv in production.
• Specify node 6.2.0.
• Use ES6 promises with Mongoose.
• Add PORT to .env.example.
• Simplify login code.

Meganote Client updates

• Set a custom page title for each state.
• Clear flash messages when exiting a state.
• Add a spinner, displayed on Sign Up only for now.
• Use a relative path for sign-up template.
• Redirect to sign-up if notes fail to load.
• Concatenate vendor JS files.
• Uglify bundle and vendor JS files.

Homework

Get your Meganote Server running on Heroku!