A butter solution to churning. We've created a single portal to track and help meet your churning goals. See a card's information you need to at a glance, and use the rewards page to view pertinent information about your points in different award programs. Need to meet minimum spend for a card with only a few days left? Buy what you need, be it Amazon credit cards(which never expire!) or your favorite book from our Amazon page so you can get that sign-up bonus and go on that trip you've been dreaming about or pocket that cash.
First, you will need to create a file named .env to conveniently record project specific environment variables. You will need one's for google authentication (see google.js), Amazon API (see amazonModel.js), and DB management (see knexfile.js). Prior to starting the server, a database must be linked through the knexfile too.
$ yarn # install dependencies
$ yarn start # start the development server
Now visit localhost:4000
There is a basic test framework in your test/ folder. Here's how to use it:
$ export NODE_ENV=Test # set environment to test to for test-specific DB
$ npm test # runs all tests
$ npm test server/index.js # runs tests in a single file- React with Redux
- Node with Express
- PostgreSQL
- Passport
- D3.js
###Hot Module Reloading Butter uses webpack's hot module reloading to update packages and refresh pages without having to restart the server or reload the page manually, making it quicker and easier to see your changes in real time. This feature is a part of our webpack setup, so all you need to do is start the server.
Our database utilizes PostgreSQL to manage information-rich tables and relationships. PostgreSQL's documentation will instruct you in setting up your local database. Our application then uses Knex migrations to quickly update schemas and also switch between database instances. By default, our application directs to development mode.
Butter uses PassportJs for Google authentication, our Passport information is located in directory location '/server/config'
Application id and secrets for Google are stored in environment variables CONKEY (for id) and CONSECRET (for secret).
Remember to store .env file in the root of the application and utilize dotenv node module.
-
User info
- A logged in users info has reference in the request body server-side within the request.user attribute.
-
Emails
- A user must allow access to their google email address for the app to log them in.
We are using the Amazon Product Advertising API for our amazon page. This allows a user to search for an Amazon product on our website and then click on that item to take them to the Amazon page where they can purchase it. When a user clicks our application's ID is associated with that click, which means we'd get the referral fees. As with any API key, don't upload yours online by writing it into your server file and then pushing that up. Store it and any other user specific information as an environment variable in a .env file.
- Joey Steinberger - Product Owner - @Josamuel on Github
- Darion Freeman - Scrum Master - @Darionfman on Github
- Jason Barnett - Team Member - @jhbarnett on Github
- Calvin Kniffin - Team Member - @calkniffin on Github
- Robert Guajardo - Team Member - @Robalexg on Github
Copyright (C) 2016 ChurnDownForWhat
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.