Poyraz Avsever
950522d467
- Updated the registration flow to check if the first admin account has been created, preventing further public registrations. - Introduced `is_first_admin_setup_available` function to determine registration availability. - Modified the `/register` and `/login` pages to redirect based on the setup state. - Enhanced the user creation process to handle internal admin accounts correctly. - Added migration script to enforce the new registration rules in the database. - Refactored chat API to improve message handling and context building. - Updated dashboard and settings components for better state management. - Improved error handling and user feedback across various components.
1.3 KiB
1.3 KiB
Database Query Order
This file is the canonical order of SQL files for database setup and migration.
| Order | SQL file | Documentation | Status |
|---|---|---|---|
| 0001 | supabase/schema.sql |
docs/database/0001-initial-schema.md |
Baseline registered |
| 0002 | supabase/migrations/0002_add_freelancer_os_core_tables.sql |
docs/database/0002-freelancer-os-core-tables.md |
Pending execution |
| 0003 | supabase/migrations/0003_add_project_planning_assets.sql |
docs/database/0003-project-planning-assets.md |
Pending execution |
| 0009 | supabase/migrations/0009_lock_registration_after_first_admin.sql |
docs/database/0009-lock-registration-after-first-admin.md |
Pending execution |
| seed-0001 | supabase/seeds/0001_demo_freelancer_os_data.sql |
docs/database/seed-0001-demo-freelancer-os-data.md |
Optional demo seed, pending execution |
How To Add The Next Query
- Create a new SQL file under
supabase/migrations/. - Use the next order number.
- Add a documentation file under
docs/database/. - Register both files in this table.
- After running the SQL, add an entry to
query-log.md.
Seed Files
Seed files are optional and should live under supabase/seeds/.
They must also be documented and registered in this file, but they should only be run in local/demo environments unless explicitly approved.