This is a Flask web application that is running on heroku. It will store account transactions and categorize them for proper budgetting.

There is a viewable demo with some dummy data to showcase the application: http://budgeting-bob-demo.herokuapp.com/. Login credentials for the demo are: username = demo and password = demo.

EDIT: The above demo doesn't work anymore since heroku changed their stance on free-tier resources (read more here).

Create a virtualenv named venv and then pip install -r requirements.txt.

To run the webapp locally, use docker-compose:

docker-compose build
docker-compose up --force-recreate

This will start-up the app and a local postgres database (with some initialized dummy data). To restart the database, you need to have the local volume deleted:

docker-compose down -v

The local docker doesn't have any user authentication, this is activated with LOCAL_MODE=true and it skips the user session logic from Flask. Logging in and Registering a user can still be access (by directly going to /login and /register), but is not needed for the local usage.

To avoid having multiple users using a single instance of this (that's not a feature I wanted to build out) I limited the login and registration to only work for 2 usernames. This way I have public access to my own instance and its password protected to avoid others from accessing it.

The second username is made available for the demo usage.

The current Upload Statements feature takes CSV's from RBC and uses those to populate all the fields for the transactions.

This service is currently setup to be deploy to Fly.io.

Changes are build and deployed by merging to master branch. Github actions handle all the steps needed to create the image and deploy it to all the fly.io environments (demo and prd).

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

MIT