Talha Ahmed
1ae5249d18
Deploy to S3 / deploy (push) Successful in 37s
Details
The banked PDF now lives IN the database (new cv_bank_files table, manual migration 010, auto-applied at startup) instead of the container filesystem, so production redeploys cannot lose a stored CV; upload writes row + bytes in one commit and creates no disk file at all. New GET /candidate/cv-bank/file serves the bytes for both download and the in-app preview. Per user request, banking a CV with a detectable email also creates or reactivates the candidate account (same pattern as manual add, no setup email), so banked people appear on the Candidates screen; a CV without an email still banks fine, account-less. Existing bank rows were backfilled locally. E2E-verified: upload -> bank row + DB bytes + zero disk files, preview and download served from the DB, candidate visible on the Candidates screen. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| index.html | ||