White Povar Project Rules

Guidelines for developing the White Povar application, a Flutter frontend with Supabase backend and Firebase integration.

Credentials & Configuration

Backend Environment

Frontend Environment

Recent Changes (2025-08-11)

When working with this codebase, be aware of these recent updates:

1. **Dependencies**: Added `supabase_flutter` and enabled `firebase_core`, `firebase_auth` in `frontend/pubspec.yaml`

2. **Config updates**: `frontend/lib/core/config/app_config.dart` defaults aligned with current Supabase project

3. **Upload fix**: Corrected `Uint8List` upload implementation in `frontend/lib/core/services/supabase_service.dart`

4. **Build verification**: `flutter build web` confirmed working

Development Workflow

Security Best Practices

1. **Never commit secrets** to source control

2. **Local builds**: Use `--dart-define` flags to inject environment variables

3. **CI/CD**: Configure secrets injection for web/mobile builds

4. **Production deployments**: Use CI secrets for credential injection

Firebase Configuration

Supabase Setup

Pending Tasks & Watchouts

When making changes, keep these items in mind:

1. **Backend security**: Replace `SECRET_KEY` placeholder in `backend/.env` for production deployments

2. **Database security**: Verify all RLS policies in Supabase are properly applied

3. **Build pipeline**: Update CI/CD to inject dart-defines for web/mobile builds

4. **Environment consistency**: Ensure all environments (dev/staging/prod) have complete credential sets

File Structure Reference

Key files to be aware of:

Build Commands

Local Development

```bash

flutter run --dart-define=SUPABASE_URL=<url> --dart-define=SUPABASE_ANON_KEY=<key> --dart-define=API_BASE_URL=<url>

```

Web Build

```bash

flutter build web --dart-define=SUPABASE_URL=<url> --dart-define=SUPABASE_ANON_KEY=<key> --dart-define=API_BASE_URL=<url>

```

Constraints