https://github.com/bdefore/cashtracker
A basic demo in the spirit of Where's George, using node.js, Express, MongoDB, CoffeeScript, Mocha, and the Bootstrap library
https://github.com/bdefore/cashtracker
Last synced: over 1 year ago
JSON representation
A basic demo in the spirit of Where's George, using node.js, Express, MongoDB, CoffeeScript, Mocha, and the Bootstrap library
- Host: GitHub
- URL: https://github.com/bdefore/cashtracker
- Owner: bdefore
- Created: 2012-08-28T23:10:38.000Z (almost 14 years ago)
- Default Branch: master
- Last Pushed: 2012-08-29T00:14:13.000Z (almost 14 years ago)
- Last Synced: 2025-02-07T12:48:12.272Z (over 1 year ago)
- Language: JavaScript
- Size: 555 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README
Awesome Lists containing this project
README
This is a codebase primarily from December 2011, as a result it is designed and tested to run on Express 2.5.11 and Node 0.6.20. It currently does not work on Express 3.0 due to the removal of dynamicHelpers.
Before running your own you will need to assign your own Facebook and MongoDB settings to development.json and production.json in src/config. You can create your own unique application on developers.facebook.com.
Local Development Steps:
MongoDB:
Install MongoDB. Create a database named 'cashtracker'. Then run 'mongod' to start the service.
Ensure your development.json file pointing to the correct path. For my development, my local path was 'mongodb://localhost/cashtracker'
I recommend using nave to manage different Node.JS installations. After installing nave, you can run the project in the following steps:
nave install 0.6.20
nave use 0.6.20
npm install -d
At which point you may run run the following from the main root dir to start Jitter which will watch for code changes, run Mocha tests, and restart the local node server accordingly:
NODE_ENV=development PORT=3000 vendor/jitter/bin/jitter -lt src/coffee src/js src/js/app.js
That's it, you may begin coding. As changes are made to the src/coffee directory, they are linted and recompiled into src/js, tests are run, and the node server restarted. This workflow is enabled by Jitter.
Heroku Development Steps:
You'll want to set up a free Heroku account along with the MongoDB add-on. The free option should suffice for testing.
More info about using Heroku toolkit here: https://devcenter.heroku.com/articles/nodejs
Heroku's MongoDB URL derives from a password that needs to be set here https://providers.mongohq.com/home for your 'heroku' user. Specify one there and update the src/config/production.json file or you will not be able to add/edit entries.
NOTE: Remember to set 'heroku config:add NODE_ENV=production' so that the app loads the correct configuration file.
Known Issues:
- When adding a new sighting for a bill that's already been entered, your entry for denomination is ignored in lieu of the first sighting's entry for it