Loading page...Загружаем страницу...正在加载页面...
AtlasRepo

How I Stopped Double-Posting To Adobe Stock With A One-File Upload Tracker

Описание и применение

Автор создал простой скрипт‑трэкер, который хранит список уже загруженных файлов, тем самым устраняя дублирование при повторных запусках и позволяя безопасно возобновлять работу после сбоев.

Задача

Duplicate uploads to Adobe Stock caused account flagging due to non-atomic upload steps and lack of a submission ledger.

Результат

The tracker eliminates duplicate uploads, allows safe partial re-runs, and runs on minimal hardware without external dependencies.

Рабочий процесс

  • Generate items.txt from asset folder
  • Run python upload_tracker.py pending items.txt to list pending files
  • Submit only files listed as pending
  • After each successful upload, run python upload_tracker.py done "asset-001.jpg" to mark as completed
  • If run fails, re-run pending to resume from last incomplete file

Доказательства

The solution is embarrassingly small. upload_tracker.py is a single Python script, standard library only, no pip install.

Источник

If the run dies at file thirty of forty, you do not want to resubmit the first thirty. But without a ledger, you have no way to know where it stopped, so you either resubmit everything or you hand‑audit the dashboard, which is exactly the kind of tedious work a pipeline is supposed to remove.

Источник

The workflow that replaced my Tuesday-night disaster: before any submission run, generate items.txt from the folder of files. Run pending first. Only submit what pending shows. Mark each file done as it goes out.

Источник

  • Дата записи: 2026-10-17T23:41:30.315Z