Dry-Run Your Asset Pipeline: Validate Covers, Zips And CSVs On A 2 GB Server
Last March I lost a full evening to a header row. I had 60 JPGs ready for Adobe Stock, generated the CSV, uploaded the batch, and every single file came back rejected in under a minute. The problem was the header. Adobe expects a specific 5-column layout, and I had written a 6th column with a field I thought was useful. One extra column, sixty rejections, zero uploads. That was the night I…
Last March, the author experienced a loss of an entire evening due to an error in a header row. They had generated 60 JPGs for Adobe Stock, uploaded the batch, and all files were rejected in under a minute. The issue was the extra column in the CSV, which Adobe expected a specific 5-column layout. The author then started validating everything before uploading, resulting in 39 finished products totaling 856 MB on a 1 vCPU, 2 GB RAM server.
The author checks the CSV headers, titles, row count, and uses a ledger to prevent double-posting. They also monitor peak RSS, not average memory usage, and render at the required resolution. Finally, they package and open the zip to ensure all files are present and correct before selling it. The author has condensed their process into four standalone Python scripts, which have caught every failure mode that used to cause evening-long troubleshooting.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
