My /ingest endpoint knew too much about validation, content hashes, PostgreSQL, S3, BullMQ and rollback. I moved these rules into a dedicated Capture Intake module without changing behavior.
I do not treat the choice of embedding model as an interchangeable environment variable. In Qdrant, it becomes part of every collection. Using different vector spaces locally and in production creates an expensive future migration.
OAuth 2.0 and OIDC return two tokens at login, and almost every implementation reads the email address from the wrong one. Why access_token and id_token serve fundamentally different purposes, and why the Userinfo endpoint is the more reliable source for user profile data.
Azurite ties the project to Azure Blob Storage. MinIO speaks the same S3 API as Hetzner Object Storage. Changing environment variables is enough to move to production. Alongside that: how the Zitadel bootstrap container creates OIDC apps automatically.
POST /ingest blocked the extension until embedding generation and the Qdrant upsert finished. BullMQ and Redis make ingestion asynchronous: an immediate 202, background processing and status queries through GET /captures/:id/status.
The Shadow DOM overlay triggered a race condition. Instagram was detected as generic, and all metadata was missing. The cause and fix using capturedElement and a previewOpen flag.
Describe your workflow. Together, we will identify the right next step.
Discuss your workflow