mirror of
https://github.com/Monadical-SAS/reflector.git
synced 2026-02-04 09:56:47 +00:00
Mathieu Virbel
3d370336cc
* fix: alembic migrations This commit fixes all the migrations that was half-backed, due to auto creation in the db init before. The process was to checkout at the commit where the migration was created, and use --autogenerate to regenerate at the state of the migration. 4 migrations was fixed. It also includes a workflow to ensure migration can applies correctly. * fix: db migration check * fix: nullable on meeting_consent * fix: try fixing tests
AWS S3/SQS usage clarification
Whereby.com uploads recordings directly to our S3 bucket when meetings end.
SQS Queue (AWS_PROCESS_RECORDING_QUEUE_URL)
Filled by: AWS S3 Event Notifications
The S3 bucket is configured to send notifications to our SQS queue when new objects are created. This is standard AWS infrastructure - not in our codebase.
AWS S3 → SQS Event Configuration:
- Event Type: s3:ObjectCreated:*
- Filter: *.mp4 files
- Destination: Our SQS queue
Our System's Role
Polls SQS every 60 seconds via /server/reflector/worker/process.py:24-62:
Every 60 seconds, check for new recordings
sqs = boto3.client("sqs", ...) response = sqs.receive_message(QueueUrl=queue_url, ...)