Express.js backend server for the Spend Wise application, providing API endpoints for transaction management and user authentication.

• 🔐 Firebase Admin SDK integration
• 📊 Transaction management API
• 🔑 API key validation
• 🌐 CORS enabled
• 📝 Request logging with Morgan
• 🔒 Environment-based configuration

• Node.js 18+
• Firebase project with Firestore
• Firebase service account credentials

1. Clone the repository:

git clone <your-server-repo-url>
cd spend-wise-server

2. Install dependencies:

npm install

3. Set up environment variables:

cp .env.example .env.local

4. Configure your Firebase credentials in .env.local:

FIREBASE_CLIENT_EMAIL=your-service-account-email@project.iam.gserviceaccount.com
FIREBASE_PRIVATE_KEY="-----BEGIN PRIVATE KEY-----\nYour Private Key Here\n-----END PRIVATE KEY-----"

Start the development server with hot reload:

npm run dev

The server will start on http://localhost:3001

Start the production server:

npm start

• GET /api/health - Server health status

• GET /api/transactions - Get user transactions
• POST /api/transactions - Add new transaction
• DELETE /api/transactions/:id - Delete transaction (soft delete)

• POST /api/validate-key - Validate user API key

This server is configured for Vercel deployment. The vercel.json file contains the necessary configuration for serverless functions.

1. Install Vercel CLI:

npm i -g vercel

2. Deploy:

vercel

3. Set environment variables in Vercel dashboard:
   • Go to your project settings
   • Add the environment variables from your .env.local

For other deployment platforms, ensure:

• Environment variables are properly set
• The server.js file is the entry point
• CORS is configured for your frontend domain

spend-wise-server/
├── server.js          # Main server file
├── firebase-config.js # Firebase configuration
├── package.json       # Dependencies and scripts
├── vercel.json        # Vercel deployment config
├── .env.local         # Environment variables (not in git)
└── README.md          # This file

• The server uses Firebase Admin SDK for secure database access
• All transactions are soft-deleted (status set to "deleted")
• API key validation checks against user documents in Firestore
• CORS is configured to allow requests from the frontend domain

1. Fork the repository
2. Create a feature branch
3. Make your changes
4. Test thoroughly
5. Submit a pull request

MIT License - see LICENSE file for details