Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Before explaining the forever package, let's take a step back and learn about something called Node Package Manager, or npm for short. Npm is a command-line utility for interacting with a repository that aids in package installation, version management, and dependency management. There are tons of packages for Node.js, some we will use in this class are: express, express-handlebars, body-parser, mysql and of course, forever. Don't worry too much about these right now. They will be explained in due time.
Once you have a package you want to install, it can be installed with a single command-line command. Thankfully, npm is very simple to use: you only have to run npm install PACKAGE_NAME_HERE, and the specified module will be installed in the current directory under ./node_modules/. Once installed to your node_modules folder, you'll be able to use require() on them just like they were built-ins (we will explore this further in la
When your ENGR account is created, a folder called 'public_html' is created as well. This folder is your 'webspace' and anything you put in there will be available to the internet-at-large via the address http://web.engr.oregonstate.edu/~your_engineering_username
The public_html folder is the web root for your primary domain name.
This means that public_html is the folder where you put all website files which you want to appear when someone types your main domain (the one you provided when you signed up for hosting).
Or put another way, when someone types your domain name into their browser, whatever is in the public_html folder is what will be shown to them.