Implement backend API and database services in Docker setup

- Added a new `api` service for the NestJS backend, including health checks and dependencies on PostgreSQL, Redis, and MinIO.
- Introduced PostgreSQL and Redis services with health checks and configurations for data persistence.
- Added MinIO for S3-compatible object storage and a one-shot service to initialize required buckets.
- Updated the Nginx configuration to proxy requests to the new backend API and MinIO storage.
- Enhanced the Dockerfile to support the new API environment variables and configurations.
- Updated the `package.json` and `package-lock.json` to include new dependencies for QR code generation and other utilities.

Co-authored-by: Cursor <cursoragent@cursor.com>

Dockerfile

@@ -16,14 +16,17 @@ COPY . .
 # via the /relay nginx proxy at runtime (instead of hardcoding localhost)
 ENV VITE_NOSTR_RELAYS=""
 
-# Enable mock data mode — no backend API server in this deployment,
-# so auth and content use built-in mock/local data instead of timing out
+# Enable mock data mode as default — set to false to use the backend API
 ENV VITE_USE_MOCK_DATA=true
 
 # Content origin must match the seeder's ORIGIN so that relay queries find
 # the seeded data, regardless of how users access the app in their browser
 ENV VITE_CONTENT_ORIGIN=http://localhost:7777
 
+# IndeeHub self-hosted backend API (via nginx /api proxy)
+ENV VITE_INDEEHUB_API_URL=/api
+ENV VITE_INDEEHUB_CDN_URL=/storage
+
 # Build the application
 RUN npm run build