How A 2 GB Server Shaped My Pricing For Digital Kits Sold To Buyers On Three Platforms

说明与用途

作者构建了一个内存友好、幂等的流水线，实现了元数据、上传和打包的自动化，从而在三大平台上以低价销售数字产品。

问题

The author’s 2 GB RAM, 1 vCPU server crashed during parallel render jobs, leaving uncertainty about which assets had uploaded and causing a costly rebuild of the pipeline.

结果

The pipeline now reliably produces 39 finished products from a 2 GB server, with automated metadata, idempotent uploads, and packaging, allowing the author to list on three platforms at a low price while maintaining margin.

工作流

• 1. Render assets sequentially with memory limits, using subprocesses for heavy steps.
• 2. Generate platform‑specific CSV metadata with make_metadata.py.
• 3. Upload assets with upload_tracker.py to avoid duplicates.
• 4. Package final zip, cover, thumbnail, and PDF docs with pack_product.py and md2pdf.py.
• 5. Organize files in assets/, output/, packs/, research/, scripts/ folders.

证据

I had queued 40 render jobs in parallel because parallel felt faster. Python ate the memory, the OS started swapping, and the whole box froze mid-job.

来源

The biggest win was dumb: inspect previews at 60 dpi instead of rendering at 300. Same decisions, a fraction of the memory.

来源

I wrote make_metadata.py to emit exactly the header each platform demands and nothing else, because every "helpful" extra column I added was a rejection waiting to happen.

来源

The fix was embarrassingly simple: upload_tracker.py, a plain ledger with pending, done, and status commands that remembers what shipped.

来源

Two dependencies total for the whole kit. The metadata and tracker scripts use the standard library alone, so they run on the cheapest VPS you can rent with no install step at all.

来源