Skip to content

Commit b6c73fd

Browse files
Aditya-18849Aditya-18849
authored
Merge branch 'main' into feature/request-validation
2 parents 2c9689c + 91275c9 commit b6c73fd

3,808 files changed

Lines changed: 6249 additions & 653620 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎.dockerignore‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
node_modules
2+
npm-debug.log
3+
build
4+
dist
5+
.git
6+
.vscode
7+
.env

‎.github/workflows/ci.yml‎

Lines changed: 56 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
name: RIVETO CI Pipeline
2+
3+
# 1. Workflow Triggers
4+
on:
5+
push:
6+
branches: [ "main" ]
7+
pull_request:
8+
branches: [ "main" ]
9+
10+
jobs:
11+
build-and-verify:
12+
name: Build & Lint Monorepo
13+
runs-on: ubuntu-latest
14+
15+
steps:
16+
# 2. Checkout the repository code
17+
- name: Checkout Code
18+
uses: actions/checkout@v4
19+
20+
# 3. Set up Node.js environment
21+
- name: Setup Node.js
22+
uses: actions/setup-node@v4
23+
with:
24+
node-version: '20.x'
25+
cache: 'npm'
26+
27+
# 4. Install Dependencies (Skipping Root until Lint PR is merged)
28+
# - name: Install Root Dependencies
29+
# run: npm install
30+
31+
- name: Install Frontend Dependencies
32+
working-directory: ./frontend
33+
run: npm install
34+
35+
- name: Install Backend Dependencies
36+
working-directory: ./backend
37+
run: npm install
38+
39+
# 5. Run Linters (Commented out until PR #53 is merged)
40+
# - name: Run ESLint & Prettier Checks
41+
# run: npm run lint
42+
43+
# 6. Build the Frontend
44+
- name: Build Frontend (Vite/React)
45+
working-directory: ./frontend
46+
run: npm run build
47+
48+
# 7. Security Audit
49+
- name: NPM Security Audit
50+
run: npm audit --audit-level=high || true
51+
52+
# 8. Placeholder for future tests
53+
- name: Run Tests (Test-Ready)
54+
run: |
55+
echo "Tests are not fully implemented yet."
56+
# npm run test

‎.gitignore‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
node_modules/
2+
dist/
3+
build/
4+
.env
5+
.DS_Store
6+
.vscode/
7+
npm-debug.log

‎.husky/pre-commit‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
npx lint-staged

‎CODE_OF_CONDUCT.md‎

Lines changed: 79 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,79 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
6+
7+
We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
8+
9+
## Our Standards
10+
11+
Examples of behavior that contributes to a positive environment for our community include:
12+
13+
- Demonstrating empathy and kindness toward other people
14+
- Being respectful of differing opinions, viewpoints, and experiences
15+
- Giving and gracefully accepting constructive feedback
16+
- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
17+
- Focusing on what is best not just for us as individuals, but for the overall community
18+
19+
Examples of unacceptable behavior include:
20+
21+
- The use of sexualized language or imagery, and sexual attention or advances of any kind
22+
- Trolling, insulting or derogatory comments, and personal or political attacks
23+
- Public or private harassment
24+
- Publishing others' private information, such as a physical or email address, without their explicit permission
25+
- Other conduct which could reasonably be considered inappropriate in a professional setting
26+
27+
## Enforcement Responsibilities
28+
29+
Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
30+
31+
Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
32+
33+
## Scope
34+
35+
This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
36+
37+
## Enforcement
38+
39+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at:
40+
41+
- contact: nishantborude555@gmail.com
42+
43+
All complaints will be reviewed and investigated promptly and fairly.
44+
45+
## Enforcement Guidelines
46+
47+
Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
48+
49+
### 1. Correction
50+
51+
**Community Impact:** Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
52+
53+
**Consequence:** A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
54+
55+
### 2. Warning
56+
57+
**Community Impact:** A violation through a single incident or series of actions.
58+
59+
**Consequence:** A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
60+
61+
### 3. Temporary Ban
62+
63+
**Community Impact:** A serious violation of community standards, including sustained inappropriate behavior.
64+
65+
**Consequence:** A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
66+
67+
### 4. Permanent Ban
68+
69+
**Community Impact:** Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
70+
71+
**Consequence:** A permanent ban from any sort of public interaction within the community.
72+
73+
## Attribution
74+
75+
This Code of Conduct is adapted from the Contributor Covenant, version 2.1, available at https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
76+
77+
Community Impact Guidelines were inspired by Mozilla's code of conduct enforcement ladder.
78+
79+
For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

‎CONTRIBUTION.MD‎

Lines changed: 111 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,111 @@
1+
# Contributing to RIVETO
2+
3+
Thanks for contributing to RIVETO! We welcome bug reports, documentation improvements, tests, UI polish, and new features.
4+
5+
## Table of contents
6+
7+
- [What to expect](#what-to-expect)
8+
- [Reporting bugs](#reporting-bugs)
9+
- [Suggesting enhancements](#suggesting-enhancements)
10+
- [Development setup](#development-setup)
11+
- [Branching & commits](#branching--commits)
12+
- [Pull request process](#pull-request-process)
13+
- [Style & tests](#style--tests)
14+
- [Code of Conduct](#code-of-conduct)
15+
- [Getting help](#getting-help)
16+
17+
## What to expect
18+
19+
Maintainers review contributions and aim to respond within a few business days. Please be respectful and patient; requested changes are normal during review.
20+
21+
## Reporting bugs
22+
23+
1. Search existing issues to see if the bug is already reported.
24+
2. If not found, open a new issue with:
25+
- A clear, descriptive title
26+
- Steps to reproduce
27+
- Expected vs. actual behavior
28+
- Environment details (OS, Node version, browser, etc.)
29+
- Minimal reproduction or screenshots/logs
30+
31+
## Suggesting enhancements
32+
33+
Create an issue describing the change, why it’s needed, and possible approaches. If you plan to implement it, mention that in the issue so others can coordinate.
34+
35+
## Development setup
36+
37+
1. Fork the repository and clone your fork.
38+
2. Create a branch from main:
39+
40+
```bash
41+
git checkout -b feat/my-feature
42+
```
43+
44+
3. Install dependencies and start the apps you need:
45+
46+
**Backend**
47+
48+
```bash
49+
cd backend
50+
npm install
51+
npm run dev
52+
```
53+
54+
**Frontend**
55+
56+
```bash
57+
cd ../frontend
58+
npm install
59+
npm run dev
60+
```
61+
62+
**Admin**
63+
64+
```bash
65+
cd ../admin
66+
npm install
67+
npm run dev
68+
```
69+
70+
4. Configure environment files as described in the README.
71+
72+
## Branching & commits
73+
74+
- Use clear branch names: `feat/...`, `fix/...`, `docs/...`, `test/...`, `chore/...`
75+
- Prefer conventional commits when possible (e.g., `feat: add X`, `fix: correct Y`).
76+
- Keep PRs focused and reasonably small.
77+
78+
## Pull request process
79+
80+
1. Push your branch to your fork.
81+
2. Open a pull request against the main branch.
82+
3. In the PR description include:
83+
- What the change does
84+
- Why it is needed
85+
- Noteworthy implementation details
86+
- Related issue references using `#<issue-number>`
87+
4. Ensure CI passes and address review comments.
88+
89+
### PR checklist
90+
91+
- [ ] My code follows the repository style guidelines
92+
- [ ] I added tests where applicable
93+
- [ ] All new and existing tests pass
94+
- [ ] I updated documentation if necessary
95+
96+
## Style & tests
97+
98+
- Run linters/formatters before submitting.
99+
- Add or update tests for any behavior changes.
100+
101+
## Code of Conduct
102+
103+
This project follows the Contributor Covenant. By participating, you agree to uphold it. If a CODE_OF_CONDUCT.md file is missing, please open an issue.
104+
105+
## Getting help
106+
107+
If you’re unsure where to start, check issues labeled “good first issue” or “help wanted”. You can also ask questions on an issue for guidance.
108+
109+
---
110+
111+
Thank you for helping improve RIVETO.

‎README.md‎

Lines changed: 18 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010

1111
## 🚀 Overview
1212

13-
**RIVETO** is a modern, fullstack web application built for scalability, advanced analytics, and seamless payment integration.
13+
**RIVETO** is a modern, fullstack web application built for scalability, advanced analytics.
1414
It features a robust admin panel for management, user tracking, advanced UI components, and secure file/image upload via Cloudinary.
1515

1616
---
@@ -20,7 +20,6 @@ It features a robust admin panel for management, user tracking, advanced UI comp
2020
- **Frontend:** React, Tailwind CSS
2121
- **Backend:** Node.js, Express.js
2222
- **Database:** MongoDB (Mongoose ODM)
23-
- **Payments:** Razorpay Integration
2423
- **Tracking:** Custom analytics & event tracking
2524
- **UI:** Advanced, responsive design with Tailwind
2625
- **Image Uploads:** [Cloudinary](https://cloudinary.com/) for secure and performant media management
@@ -37,7 +36,6 @@ It features a robust admin panel for management, user tracking, advanced UI comp
3736
## ⚙️ Features
3837

3938
- 📊 **Admin Panel:** Manage users, payments, analytics, and more
40-
- 💳 **Razorpay Integration:** Seamless and secure payment workflow
4139
- 📈 **Advanced Tracking:** User behavior, transactions, and event analytics
4240
- 🎨 **Modern UI:** Responsive, accessible, and beautiful interface (Tailwind)
4341
- 🖼️ **Cloudinary Image Upload:** Fast, secure, and optimized media storage
@@ -199,8 +197,6 @@ RIVETO/
199197
```
200198
MONGODB_URI=
201199
JWT_SECRET=
202-
RAZORPAY_KEY_ID=
203-
RAZORPAY_KEY_SECRET=
204200
BASE_URL=http://localhost:5000
205201
206202
CLOUDINARY_CLOUD_NAME=
@@ -225,14 +221,6 @@ REACT_APP_RAZORPAY_KEY=
225221
- Custom components for user and payment management
226222
227223
---
228-
229-
## 💳 Payments
230-
231-
- Razorpay checkout integrated for secure payments
232-
- Payment status tracking and webhooks
233-
234-
---
235-
236224
## 📈 Tracking
237225
238226
- Custom event logging and analytics
@@ -252,6 +240,23 @@ Please review [CONTRIBUTING.md](CONTRIBUTING.md) for details.
252240
253241
---
254242
243+
## 🌟 Our Amazing Contributors
244+
245+
Thank you to all contributors who have helped make RIVETO better! 🚀
246+
247+
<a href="https://github.com/Nsanjayboruds/RIVETO/graphs/contributors">
248+
<img src="https://contrib.rocks/image?repo=Nsanjayboruds/RIVETO" />
249+
</a>
250+
251+
### 🏆 Special Recognition
252+
- 🎯 **First Contributor:** Madhav Majumdar ([@madhav2348](https://github.com/madhav2348)) - For being the first to join and contribute to RIVETO!
253+
- 💡 **Most Innovative:** Md Ashad ([@asadanwarr0](https://github.com/asadanwarr0)) - For enhancing the About, Contact, and Home sections.
254+
- 🎨 **UI/UX Champion:** Vedant ([@vedantbudhabaware](https://github.com/vedantbudhabaware)) - For fixing critical UI issues and optimizing the mobile experience.
255+
256+
*Want to see your name here? Check out our [Contributing Guide](contribute.md)!*
257+
258+
---
259+
255260
## 🚀 Deployment
256261
257262
- **Docker Compose** and cloud deployment instructions coming soon!

‎backend/.eslintrc.json‎

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
{
2+
"env": {
3+
"node": true,
4+
"es2021": true
5+
},
6+
"extends": ["eslint:recommended", "prettier"],
7+
"rules": {
8+
"no-unused-vars": "error",
9+
"no-console": "warn",
10+
"no-undef": "error"
11+
}
12+
}

‎backend/.gitignore‎

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,28 @@
1+
# Environment variables
12
.env
3+
.env.local
4+
.env.*.local
25

6+
# Dependencies
7+
node_modules/
8+
package-lock.json
9+
10+
# Logs
11+
*.log
12+
npm-debug.log*
13+
yarn-debug.log*
14+
yarn-error.log*
15+
16+
# OS files
17+
.DS_Store
18+
Thumbs.db
19+
20+
# IDE
21+
.vscode/
22+
.idea/
23+
*.swp
24+
*.swo
25+
26+
# Build outputs
27+
dist/
28+
build/

0 commit comments

Comments
 (0)