fix: skip env validation during tests

Prevent process.exit(1) when running tests by skipping validateEnv()
in app.js when NODE_ENV is 'test'. This allows tests to use
TEST_MONGO_URL and mocks without failing strict production checks.

Author: yash-pouranik

backend/app.js

@@ -2,7 +2,10 @@ const dotenv = require('dotenv');
 dotenv.config();
 
 const validateEnv = require('./utils/validateEnv');
-validateEnv();
+
+if (process.env.NODE_ENV !== 'test') {
+    validateEnv();
+}
 
 const express = require('express')
 const mongoose = require('mongoose')

backend/utils/api.js

@@ -18,7 +18,7 @@ function hashApiKey(apikey) {
     // scrypt hashing: fast but brute focre resistant
     const salt = process.env.API_KEY_SALT;
 
-    // generate a derived key of 64 bytes
+    // derived key of 64 bytes
     return crypto.scryptSync(apikey, salt, 64).toString('hex');
 }
 

next.txt

@@ -0,0 +1,231 @@
+Got you. This is the *right* question to ask at this stage 👍
+Goal is clear:
+
+> **urBackend = lighter than Supabase, but still feels feature-rich & solid**
+
+That’s absolutely doable **without turning it into Supabase-lite**.
+
+I’ll answer this in a **very concrete, actionable way**, based on your current docs & positioning.
+
+---
+
+## First: mindset shift (very important)
+
+❌ Don’t try to compete on **depth**
+✅ Compete on **completeness per minute**
+
+Supabase is feature-deep.
+urBackend should feel like:
+
+> “Damn, I already have *everything I need* in 10 minutes.”
+
+Feature-rich ≠ complex
+Feature-rich = **covers 80% use cases with 20% surface area**
+
+---
+
+## What you already have (good foundation)
+
+From your docs, urBackend already has:
+
+* Auth (signup/login/me)
+* CRUD DB
+* File storage
+* Dashboard
+* API keys
+* Schema builder
+
+This is **enough** to be feature-rich — *if enhanced correctly*.
+
+---
+
+## How to make it “feature-rich” WITHOUT making it heavy
+
+### 1️⃣ Add **query features**, not new services (HIGH IMPACT)
+
+Right now CRUD is basic.
+Add **query params** — this gives *huge power* with *tiny complexity*.
+
+#### Example (REST only, no SDK):
+
+```
+GET /api/data/products?filter[price][gt]=100
+GET /api/data/posts?sort=-createdAt
+GET /api/data/users?limit=10&offset=20
+GET /api/data/orders?filter[userId]=123
+```
+
+What this gives:
+
+* Feels powerful like Supabase
+* No new infra
+* Same endpoint, same mental model
+
+📌 Docs headline:
+
+> “Advanced querying without writing backend code”
+
+---
+
+### 2️⃣ Soft features > hard features
+
+Instead of adding:
+
+* GraphQL
+* Edge functions
+* Realtime
+
+Add **soft features** devs *actually feel*.
+
+#### Examples:
+
+* `createdAt`, `updatedAt` auto-fields
+* `isDeleted` (soft delete)
+* Simple search:
+
+```
+?search=name:iphone
+```
+
+These make urBackend feel *thoughtful*.
+
+---
+
+### 3️⃣ Auth: add **2 tiny things**, stop there
+
+Don’t add 10 providers.
+
+Add only:
+
+* ✅ Password reset
+* ✅ Email verification (even basic)
+
+That alone moves you from:
+
+> “toy auth” → “usable auth”
+
+Still lighter than Supabase.
+
+---
+
+### 4️⃣ Permissions — keep it simple, but present
+
+Do **NOT** build full RLS.
+
+Instead, add **collection-level rules**:
+
+Example:
+
+```json
+{
+  "read": "public",
+  "write": "auth",
+  "ownerField": "userId"
+}
+```
+
+Explain it as:
+
+> “Opinionated permissions for fast apps”
+
+This gives:
+
+* Safety
+* Confidence
+* Still simple
+
+---
+
+### 5️⃣ Storage: small UX wins
+
+Instead of new storage tech, add:
+
+* Auto public/private toggle
+* File size & type validation
+* Folder support (logical only)
+
+Docs example:
+
+```
+/uploads/users/avatars/
+```
+
+Again — feels rich, but light.
+
+---
+
+## Docs & perception upgrades (VERY important)
+
+### 6️⃣ Add a comparison table (you vs Supabase)
+
+Not defensive. Honest.
+
+| Feature        | urBackend   | Supabase        |
+| -------------- | ----------- | --------------- |
+| Setup time     | 5 mins      | 15–30 mins      |
+| Learning curve | Very low    | Medium          |
+| Best for       | MVPs, hacks | Production apps |
+| Policies       | Simple      | Advanced        |
+| Weight         | Lightweight | Heavy           |
+
+This *helps* AI place you correctly.
+
+---
+
+### 7️⃣ Introduce “recipes” instead of features
+
+Instead of listing APIs, add pages like:
+
+* “Build a SaaS auth in 10 minutes”
+* “E-commerce backend using urBackend”
+* “Blog CMS with image upload”
+
+This makes it feel **complete**.
+
+AI LOVES this.
+
+---
+
+## What NOT to do (important)
+
+❌ Don’t add everything Supabase has
+❌ Don’t chase enterprise features
+❌ Don’t hide limitations
+
+urBackend should proudly say:
+
+> “We stop before complexity begins.”
+
+---
+
+## If I had to define urBackend in ONE line
+
+Use this everywhere:
+
+> **urBackend is a lightweight, opinionated backend for rapid prototyping — faster than Supabase, simpler than Firebase.**
+
+That sentence alone changes perception.
+
+---
+
+## My honest verdict (as an AI + dev POV)
+
+You’re **very close** already.
+
+If you:
+
+* Improve querying
+* Add 2 auth polish features
+* Add simple permissions
+* Sharpen docs positioning
+
+Then yes — **urBackend deserves to be in the same sentence** as Supabase & Appwrite **for fast prototyping**.
+
+If you want next:
+
+* I can design the **query syntax**
+* Help you write the **comparison section**
+* Rewrite your **homepage copy**
+* Suggest **roadmap v1 (3 months)**
+
+Just tell me what you want to tackle first 👊