Post-Mortem: Why My Blog Cover Images Silently Failed to Restore from S3
The article discusses the challenges faced in restoring blog cover images from AWS S3. It highlights two main issues: a fuzzy matching algorithm that failed due to concatenated filenames and the absence of AWS credentials in the local environment. The author details the solutions implemented to resolve these problems and successfully restore the images.
- ▪Six blog posts had broken cover images stored on AWS S3.
- ▪The fuzzy matcher failed because it could not tokenize concatenated filenames, resulting in no matches.
- ▪The command to restore images also failed due to missing AWS credentials in the local environment.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 126345) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Vicente G. Reyes Posted on May 22 • Originally published at vicentereyes.org Post-Mortem: Why My Blog Cover Images Silently Failed to Restore from S3 #python #django #aws #api Six blog posts on my portfolio had broken cover images for longer than I'd like to admit. The images were in S3. The management command to restore them had been written and run. And yet — nothing. Blank covers, every time. Here's the full breakdown of what went wrong, why, and how it got fixed.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
