e5e56e48f8
- Integrated SpamDetector utility to check for spam patterns in team names and user names during signup and invitation processes. - Enhanced TeamMembersController to log and block obvious spam invitations while allowing suspicious ones for review. - Updated passport-local-signup strategy to flag high-risk signups and log details for admin review. - Added moderation routes to handle spam-related actions and integrated rate limiting for invitation requests. - Improved frontend components to provide real-time spam warnings during organization name input, enhancing user feedback.
All database DDLs, DMLs and migrations relates to the application should be stored here as well.
Worklenz Database
Directory Structure
sql/- Contains all SQL files needed for database initializationmigrations/- Contains database migration scripts00-init-db.sh- Initialization script that executes SQL files in the correct order
SQL File Execution Order
The database initialization files should be executed in the following order:
sql/0_extensions.sql- PostgreSQL extensionssql/1_tables.sql- Table definitions and constraintssql/indexes.sql- All database indexessql/4_functions.sql- Database functionssql/triggers.sql- Database triggerssql/3_views.sql- Database viewssql/2_dml.sql- Data Manipulation Language statements (inserts, updates)sql/5_database_user.sql- Database user setup
Docker-based Setup
In the Docker environment, we use a shell script called 00-init-db.sh to control the SQL file execution order:
- The shell script creates a
sql/subdirectory if it doesn't exist - It copies all .sql files into this subdirectory
- It executes the SQL files from the subdirectory in the correct order
This approach prevents the SQL files from being executed twice by Docker's automatic initialization mechanism, which would cause errors for objects that already exist.
Manual Setup
If you're setting up the database manually, please follow the execution order listed above. Ensure your SQL files are in the sql/ subdirectory before executing the script.