Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/pranavgoel29/chippin

Expense tracker with Split Functionality
https://github.com/pranavgoel29/chippin

budget-app graphql postgresql react react-hook-form reactjs typeorm typescript vite

Last synced: 11 days ago
JSON representation

Expense tracker with Split Functionality

Awesome Lists containing this project

README

        

logo

# Chippin

In the Works 🔥,
Expense tracker

## 🚀Features

- Add Budgets
- Add expenses
- Manage expenses

## 📦About Project

Tech Stack:

- React
- TypeScript
- GraphQL
- Type ORM
- PostgresSQL
- React-Hook-Form
- Styled-Components
- Vite

## Getting Started
1. Start the Redis server to initiate the redis instance. (Only applicable if you are using redis locally)

#### For backend
1. Run the watch command. (This will constantly watch over the code and transpile the TS into JS for the build)
2. Run dev/build accordingly.

- Make sure if you are using the cloud redis client to update in the index file and make an `env` with your redis keys.

- Put the 'host' link provided by the redis cloud client as the value for the `REDIS_HOST`. And put the 'passwrod' provided by it as the value of `REDIS_PASSWORD`. And at last don't forget to also put the `port` value for `REDIS_PORT`.

This will allow your Redis to connect with the project.

#### For Client
1. Run the 'gen' command present in `package.json`. (This command will generate the graphQL functions and hooks, this will only run when backend is already spun up)
2. Secondly run the dev command to start the client.

## 📷Screenshots
![Login Page Screenshot](./screenshots/login.png)

![Register Page Screenshot](./screenshots/register.png)

![Dashboard Page Screenshot](./screenshots/dashboard.png)

![Expenses Page Screenshot](./screenshots/expenses.png)

![User Page Screenshot](./screenshots/userpage.png)
## 🐛Bug Reporting

Feel free to [open an issue](https://github.com/pranavgoel29/Chippin/issues) on GitHub if you find any bug.