Temple-Expenses-Management

🛕 Temple Management Backend

A backend system built with Node.js and Express to power a temple website management platform. It offers RESTful APIs for managing donations, donors, expenses, events, reports, and user authentication, including a secure password reset mechanism.

✨ Features

🔐 User Authentication & Profile

Login via username + password or mobile number.
Mobile login supports password reset flow.
Password reset requires users to set a new password before proceeding.
Profile page to view and update password securely.

📁 CRUD Operations

Manage core temple data:

Donations
Donors
Expenses (with image upload via Multer)
Events
Reports

Each supports Create, Read, Update, Delete operations.

📊 Derived Reports

Aggregate donor reports with event-based filtering.

🧭 API Routes

Endpoint	Method(s)	Description
`/api/login`	POST	Login with username/password or mobile number (reset flow)
`/api/users`	GET, POST	Get all users / Create a new user
`/api/users/:id`	PUT	Update user info (e.g., password)
`/api/donations`	CRUD	Manage donations
`/api/donors`	CRUD	Manage donors
`/api/expenses`	CRUD	Manage expenses with image upload
`/api/events`	CRUD	Manage events
`/api/reports`	CRUD	Manage reports
`/api/derived-donors`	GET	Aggregate donor report, filterable by event

🔁 Password Reset Flow

User attempts login via mobile number.
Backend verifies the mobile number.
User is prompted to reset the password.
User updates password via PUT /api/users/:id.
User logs in again using the new password.

⚙️ Setup Instructions

Clone the repository:

git clone https://github.com/your-username/temple-management-backend.git
cd temple-management-backend

Install dependencies:
```
npm install
```
Start the backend server:
```
node backend/server.js
```
Visit: http://localhost:5000

🔗 Frontend Integration Notes

Set JSON headers in all API requests:

headers: {
  "Content-Type": "application/json"
}

Example password update request:
```
{
  "password": "newPassword123"
}
```
After reset, clear saved session/localStorage and redirect to login.

⚠️ Important Notes

Passwords are stored in plaintext in users.json (for demo).
🔐 Implement hashing for production.
Uses local storage with data/*.json files.
Static files served from /public and /admin.
Expense images are uploaded using Multer.