Back to feed
Dev.to
Dev.to
6/26/2026
How I built the OSS alternatives directory: GitHub ETL, Turso, and the UPSERT trap I hit

How I built the OSS alternatives directory: GitHub ETL, Turso, and the UPSERT trap I hit

Short summary

The author built an OSS alternatives directory using GitHub ETL, Turso libSQL, and Claude Haiku for AI-generated content. A critical lesson: using ON CONFLICT DO NOTHING prevented content updates, so they switched to DO UPDATE for the content table. They optimized costs by using Claude prompt caching on batch operations.

  • •ETL architecture: seed from JSON, fetch fresh GitHub data, generate content with Claude Haiku
  • •Fixed UPSERT bug: DO NOTHING prevented overwriting stale generated content; switched to DO UPDATE
  • •Reduced token costs using system-prompt caching for repetitive Claude calls

Generated with AI, which can make mistakes.

#open-source#ai-tools#ai-agents
Read full article at Dev.to

Is this a good recommendation for you?

Comments

Failed to load comments. Please try again.

Explore more

26 Repos in 29 Days With an AI Pipeline: What Actually Broke
Dev.to
Inside the Pipeline Powering a Korean Entertainment MCP Server
Dev.to
How I built pairwise AI model compare pages with Claude Haiku and a budget cap
Dev.to
The original title is "Bootstrapped Data Products — Here's What I Learned"
Dev.to