mohnish / money

Money - let's you manage your money and visualize where your money goes. Built using Ruby 2.3.0, Rails 4.2.5, Backbone and Bootstrap

Money

Money (beta) is an app to manage your bills and payments. It helps you reach your financial goals by showing you where you have been spending the most and where you can save.

Introduction blog post https://mt.cx/money

Features

• Add bills (recurring ones and one time)
• Reports. Neat graphs showing where your money went
• Get reminders about bills [WIP]

Development

Before you continue, make sure you have the correct version of Ruby installed on your machine. For Ruby installation information, please refer to the docs/installing_ruby.md file.

from the application root, run the following commands

• bin/setup - sets up the app
• bin/rspec - run tests
• bin/rake jasmine:ci - runs js tests

Running the app

from the application root, run

• bin/rails s

This will start the server @ http://localhost:3000/

If you had run the bin/setup earlier, you'll have access to seed data and you can use username: bond and password: test1234 to login to the app.

Deploying

API

API docs [TODO]

Technologies Used

• Rails 4.2.5
• Ruby 2.3.0
• Backbone 1.2.3
• Bootstrap 3.3.6

</> with <3

License

(The MIT License)

Copyright (c) 2016 Mohnish Thallavajhula <[email protected]>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

money's Issues

add tags to bills while creating

add guide docs/faqs/help docs

• add ruby installation docs
• deploy help

add pagination

tags

• create tags
• delete tags

user signout

add notes to payments

the backend currently handles this. need to implement this on the frontend.

routes

• GET /api/categories
• POST /api/users/:user_id/bills/:bill_id/tags
• DELETE /api/users/:user_id/bills/:bill_id/tags/:id
• GET /api/users/:user_id/bills/:bill_id/payment_sources
• POST /api/users/:user_id/bills/:bill_id/payment_sources
• PATCH /api/users/:user_id/bills/:bill_id/payment_sources/:id
• PUT /api/users/:user_id/bills/:bill_id/payment_sources/:id
• DELETE /api/users/:user_id/bills/:bill_id/payment_sources/:id
• POST /api/users/:user_id/bills/:bill_id/payments
• DELETE /api/users/:user_id/bills/:bill_id/payments/:id
• GET /api/users/:user_id/bills
• POST /api/users/:user_id/bills
• GET /api/users/:user_id/bills/:id
• PATCH /api/users/:user_id/bills/:id
• PUT /api/users/:user_id/bills/:id
• DELETE /api/users/:user_id/bills/:id
• POST /api/users
• GET /api/users/:id
• PATCH /api/users/:id
• PUT /api/users/:id
• DELETE /api/users/:id

bootstrap categories and repeat intervals data to the create bill view

currently these values are being loaded after the view is loaded which wastes a noticeable amount time. it'd be better to bootstrap this data to the view when it's loaded.

Display graphs showing the categories of expenditure

activate user

• verify the user
• set a verified flag on the user

allow user to select payment source when a non-repeating bill is being added

currently the UI doesn't have the option for non-repeating bills

this should be done after the implementation of payments

user profile page

• display profile pic using gravatar for now

dry out the json responses into partials

do something similar to what was done with the bills responses

after adding a bill frontend seems to be getting botched

• tags are not being displayed on the frontend
• clicking the bill doesn't navigate to the show bill page (this happens only after adding the bill)
• the profile link is broken after adding a bill

payment sources

• create payment sources
• display payment sources

the date should always default to todays date

add backend logic for updating next_due_date on payment creation

setup travis

• travis ci or maybe circle ci

toggle select card

selecting never on bills form should display select card on the form

add new relic to track errors and performance

UI improvements

• reduce the content of each bill on the bills page. this data is already available in the show bill page, so it should be fine. keep only the pieces of info that's absolutely necessary. #38
• update the position of the condensed bills to make 'em look as if they're aligned with the form #49
• selecting never on bills form should display select card on the form #32
• collapse the bills form by default #41
• collapse the payments form by default #42
• update the next_due_date on creation of payment (based on the repetition interval) #43
• turn off autocomplete for some of the fields (needs review) #44
• auto lowercase the username field (autocapitalize="off" on the text field) #45
• the date should always default to todays date #46

remove the "*" from the tags input field in the bills form

refer to the following image. tags are not mandatory for bill creation. so remove the asterisks

update bills template

reduce the content of each bill on the bills page. this data is already available in the show bill page, so it should be fine. keep only the pieces of info that's absolutely necessary.

collapse the bills form by default

Sort bills based on amount spent, items purchased etc

add backend logic for creating payment when the repeat interval is "never"

handle 401s properly all over the app

implement navigation from profile to bills and bill to bills

• profile -> bills
• bills -> profile

Display bills based on week, month, year and date range

user signup

turn off autocomplete for some of the fields (needs review)

user signin

dom renders fully every single time an item is added to the collection

use a common event dispatcher across the entire app for navigation

currently the views are managing the dispatch calls. we need this to be done by the common dispatcher. the current navigation mechanism wouldn't scale after the features are implemented. need to do it as part of the 2nd release.

read data from a receipt. OCR capabilities

• take a pic
• use ocr to read the data from it
• save it to the db

collapse the payments form by default

suggest tags based on input

• populate tags as you type

update the position of the condensed bills to make 'em look as if they're aligned with the form

graphs/reports

• based on the category of purchase
• based on the payment source
• based on the month

payments implementation

• create payments from the app
• display payments

set payment amount default to bill amount

Support login with email or username

current the app only supports login with username

users endpoint

update the next_due_date on creation of payment (based on the repetition interval)

for non-repeating bills selecting never should autopopulate next due date to current data

notifications implementation

• updates for the app when the user logs in
• need to support notifications

auto lowercase the username field (autocapitalize="off" on the text field)

bills

• Create
• Retrieve

frontend model structure seems to be different from the backend models

this is causing a few issues:

• for nested models, the validations fail due to the fact that the id attributes for the corresponding belongs_to relation are not populated in the responses.

for ex:

on the frontend, the payment looks something like this:

{
  bill_id: 1,
  bill: { id: 1, name: 'foo' }
}

this passes frontend validation since the bill_id is populated. but the problem arises when we get a collection back from the server and the individual models look something like this:

{
  bill: { id: 1, name: 'bar' }
}

this is an invalid model from the frontend's perspective since the bill_id attr is missing.

• due to this, after creating a payment, it gets inserted into the db but on the frontend, the collection fails to update. this is because the collection already has models that fail frontend validations.

style bills page and make it look cleaner

update the position of the condensed bills to make 'em look as if they're aligned with the form