Ecosyste.ms: Awesome

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

Awesome Lists | Featured Topics | Projects

https://github.com/murodjon000/transaction_group_app

Transaction app is a web app that allows you to group payments with your friends and family.
https://github.com/murodjon000/transaction_group_app

bootstrap4 rails rspec

Last synced: about 1 month ago
JSON representation

Transaction app is a web app that allows you to group payments with your friends and family.

Awesome Lists containing this project

README

        

# Transaction app

> Transaction app is a web app that allows you to group payments with your friends and family.
> ![App](./app/assets/images/app.png)

# Transactions page

> ![App](./app/assets/images/app3.png)

# External Transactions page

> ![App](./app/assets/images/app1.png)

# All Groups page

> ![App](./app/assets/images/app2.png)

## Features

- User can signup and login
- Guest user can't access any other page in the app except login and signup pages
- Logged in user can access her and only her profile page
- Profile page provides links to "All my transactions", "All my external transactions" and "All groups"
- Logged in user can view all his transactions and create new ones which can be assigned to a group
- Logged in user can view all groups and create a new
- Logged in user can visit show page of a group which will list all payments associated with it
- Followed TDD

The data models were constructed according to the following Entity Relationship Diagram(ERD):

> ![ERD](./app/assets/images/diagram.png)

## Live Demo

- [transaction-app-ror](https://transaction-app-ror.herokuapp.com/)

## Built With

- Ruby v2.6.5
- Ruby on Rails v6.0.2
- VSCode - code editor

## Getting Started

- Clone the repo `https://github.com/Murodjon000/ror_capstone_transaction_app.git`
- cd `into` the project
- Run `git pull origin transiction`
- Run `bundle install`
- Run `yarn install --check-files`
- Setup your `db` in the `database.yml` and run `rails db:setup`
- Run `rails s` and visit `localhost:3000`

### Github Actions

To make sure the linters' checks using Github Actions work properly, you should follow the next steps:

1. On your recently forked repo, enable the GitHub Actions in the Actions tab.
2. Create the `feature/branch` and push.
3. Start working on your milestone as usual.
4. Open a PR from the `feature/branch` when your work is done.

### Run tests

- Run `bundle exec rspec` to run all the tests

## Author

👤 **Murodjon Tursunpulatov**

- Github: [@murodjon000](https://github.com/murodjon000)
- Twitter: [@MurodjonTursun5](https://twitter.com/MurodjonTursun5)
- Linkedin: [@Murodjon Tursunpulatov](https://www.linkedin.com/in/murodjon-tursunpulatov-5189481b3/)

## Acknowledgments

The design of the project was inspired by [Snapscan](https://www.behance.net/gallery/19759151/Snapscan-iOs-design-and-branding) by [GregoireVella](https://www.behance.net/gregoirevella).

## 🤝 Contributing

Contributions, issues and feature requests are welcome!

Feel free to check the [issues page](https://github.com/Murodjon000/ror_capstone_transaction_app/issues).

## Show your support

Give a ⭐️ if you like this project!

## 📝 License

MIT License

Copyright (c) 2021 Murodjon Tursunpulatov

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.