https://www.jamieede.com/tags/devops/ Recent content in DevOps on Jamie Ede Hugo en-us Thu, 21 May 2026 16:00:00 +0000 https://www.jamieede.com/posts/re-ingesting-rag-doc-corpus-when-docs-change/ Thu, 21 May 2026 16:00:00 +0000 https://www.jamieede.com/posts/re-ingesting-rag-doc-corpus-when-docs-change/ <p>The <a href="https://www.jamieede.com/astra-chat" >Astra Docs Chat</a> corpus was loaded once. DataStax ships doc updates regularly; v1 does not auto-refresh. This post outlines a repeatable re-ingest strategy when the markdown export changes: what to detect, how to use existing resume tooling, and when full rebuild beats incremental upsert.</p> <p>Series: <a href="https://www.jamieede.com/posts/building-astra-docs-chat-rag-over-datastax-on-langflow-and-cloudflare-pages/" >Building Astra Docs Chat</a> · <a href="https://www.jamieede.com/posts/batch-ingest-markdown-langflow-api/" >Batch ingest script</a> · <a href="https://www.jamieede.com/posts/chunking-embedding-technical-docs-rag/" >Chunking and embedding</a> </p> <p>Try the chat: <a href="https://www.jamieede.com/astra-chat" >Astra Docs Chat</a> </p> <hr> <h2 id="when-manual-re-ingest-is-enough" class="anchor-link"><a href="#when-manual-re-ingest-is-enough">When manual re-ingest is enough<span class="pilcrow">&nbsp;¶</span></a></h2> <p>For a personal reference tool, running ingest after major doc releases (or when answers feel stale) may be sufficient. No cron, no diff pipeline, just:</p>