How Upload_Tracker.Py Stops Double-Posting When You Re-Run A Batch
I run my whole asset pipeline on a 1 vCPU, 2 GB RAM box with no GPU. A few months ago I had a batch of 40 sticker assets ready for Adobe Stock, Vecteezy, and Dreamstime. The CSV was built, the files were named, everything looked done. Then the SSH session dropped halfway through my upload queue. I reconnected, re-ran the batch script from the top, and went to make coffee. When I came back I had…
Upload_Tracker.py is a Python script that prevents double-posting when running a batch of assets for online platforms. It works by keeping a ledger of uploaded assets in a text file and checking this ledger before attempting to upload any files. If the process is interrupted during an upload, the asset remains pending for the next run, ensuring that no duplicates are submitted.
The script uses the standard library alone, making it lightweight and easy to integrate into existing asset pipelines. The key insight is that the ledger should be updated after the upload succeeds, not before, allowing the script to pick up unfinished uploads on subsequent runs. This simple approach has prevented double-posting in the author's experience and has become an essential part of their asset submission process.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
