Backbone website - gobackbone.com
- Node.js 6.11.1 (Use the exact version as this is currently the Node.js version we use in AWS)
Use Yarn instead of npm to install package dependencies. Using Yarn will ensure you get the same dependency versions. Assuming you already have Yarn installed, simply run yarn install from the project root.
Ensure the Backbone API server is running before launching the web server.
Ask another developer for the following environment variables values, which you'll store in your .env.local file (create the file if it doesn't already exist):
- BL_MAILGUN_API
If the package is required by the production Webpack build, make sure to install the package as a production dependency as opposed to a dev dependency. Otherwise, packages not required in the production environment can be installed as dev dependencies.
Production releases should be triggered from the production branch. Therefore, master could be ahead of production because we may merge in new changes but delibrately hold off on releasing until a later time. Using a separate branch for releases will allow us to further test and perform QA before releasing to the wild.
- Make sure you have the Elastic Beanstalk CLI installed and configured. See http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb-cli3.html.
- If deploying to staging, checkout to the
masterbranch and runeb deploy backbone-web-staging - If deploying to production, checkout to the
productionbranch, merge in the latestmaster, and runeb deploy backbone-web-prod