This is a sample e-commerce application to demonstrate the end-to-end usage of the NERP stack.
- Node (>6.7) and npm
- PostgreSQL
npm install
npm run seed
npm run build-watch
npm run dev
The above script will go through the following steps:
- install npm dependencies
- populate your Postgres DB with the seed data in
db/seed.js
- perform a build with Webpack and watch for changes
- run the server and watch for file changes with nodemon
All pushes to GitHub are being built and tested by Travis CI. However, only a select few of these builds will be deployed to Heroku.
We have two versions of the app on Heroku:
Prod: https://just-home.herokuapp.com/
Test: https://just-home-test.herokuapp.com/
Right now, only branches specified in our .travis.yml
file will be deployed to Heroku by Travis CI. You can mark a branch for deployment to Test by editing the following section like so:
...
app:
master: just-home
your_branch: just-home-test
...
If you do this, be sure not to change the other branches and their deployment targets.
All deployments to Prod will go through the following process:
- A feature branch opens up a Pull Request on
master
- The branch is built and tested by Travis CI
- If the build/tests pass, GitHub will allow collaborators to complete the merge
- Once the PR is merged, Travis will rebuild the repo and deploy to Prod
No changes need to be made to the .travis.yml
file to enable this process. Be sure not to directly push to master
in an effort to avoid bad builds being deployed to Prod.
The easiest way to test is with Postman. You can use our development testing collection to help you get started!