Identify your mongo db url used previously. Ask JR for a shared mongo db url if needed.
We will configure the mongo db url on aws as well as in our local environment.
Be able to do the following:
-
understand changes required for production deployment to aws
-
update your week-10 storefront api for deployment to aws
-
deploy your updated repository to aws
-
add your mongo db url as an environment variable on aws
-
understand heroku deployment
-
install the heroku cli
-
login to heroku from the cli
-
configure environment variables on heroku
This readme outlines all of the changes included in this repository that allow aws deployment.
After an overview, you will make changes to your week 10 repository and deploy it to aws.
You will commit your changes to your week 10 repository and create a new PR.
New this week is AWS and Heroku deployment and the changes that were made to support the deployment process.
Below we list out changes required from the original development-only version we previously built.
-
Changed the "start" script to use "node" in place of "nodemon". Nodemon is for development only.
-
Added a "dev" script to support using nodemon in development.
-
Added a "zip-for-aws" script to zip content for deployment to aws.
-
Installed
env-cmdandarchivernode modules
env-cmd allows us to have a .env file in development to configure our MONGO db url safely where the setting is not shared in git.
archiver supports a script to run to generate the zip file that aws requires for the aws web console upload.
-
Updated "port" settings to allow the production server to set the port value.
-
Added configuration check for MONGO_URL environment variable and start DB only when configured.
See AWS.md and HEROKU.md
We built this repo in week 10 and then updated it for week 12 as an introduction to connecting an express node app to a mongo database.
This app was configured originally only for development and required additional work this week for production readiness.
Previous versions: