Nuxt Content 3 content update on prod
Using Nuxt Content 3 and Nuxt 4 SSR/ISR is it possible to update only the Markdown based content of the site without needing to rebuild and redeploy the whole app?
I'm thinking about a solution where the app and the content live in separate git repositories. The app is running in a docker container on a VPS. The content is cloned on the same VPS and it is mounted as the /content directory of the app.
Whenever there is a push against the content repo the server is notified to pull the content changes and the app is notified to reindex the content (ideally the changed files only).
Based on my understanding parsing and indexing in the prod app is not possible but maybe there is a way. Do you know any?
5 Replies
Hi @gourangaguerrilla. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
With Nuxt Content 3, the content is parsed and indexed into a database (SQLite or other adapters) during the build or pre-rendering phase. In production, Nuxt Content v3 does not support live parsing or re-indexing of new or changed Markdown files on the fly. The content is bundled into a database dump, which is restored at runtime for fast queries and client-side navigation. This architecture is designed for performance and scalability, especially for serverless and edge deployments, but it means that content changes are not picked up automatically in production without a rebuild or redeploy of the app Nuxt Content v3 Advanced Database Nuxt Content v3 Blog.
Your idea of mounting the content directory and pulling updates from a separate git repo is technically possible for file access, but Nuxt Content v3 will not automatically re-parse or re-index the new Markdown files in production. The documentation does not mention any built-in mechanism to trigger a reindex or partial re-parse of content files in a running production app. All content is processed and the database dump is generated at build time, and this dump is what is used in production.
Summary:
- Live content updates without rebuild/redeploy are not supported in Nuxt Content v3 production. - Content changes require a new build to be parsed and indexed into the database dump. - There is no documented API or CLI to trigger reindexing of only changed files in production. If you need live content updates, you would need to trigger a rebuild/redeploy of your Nuxt app whenever content changes are pushed. This is a design choice for performance and consistency in Nuxt Content v3 Nuxt Content v3 Advanced Database. If you need more dynamic content updates, you may need to consider a headless CMS or a different architecture. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------
- Live content updates without rebuild/redeploy are not supported in Nuxt Content v3 production. - Content changes require a new build to be parsed and indexed into the database dump. - There is no documented API or CLI to trigger reindexing of only changed files in production. If you need live content updates, you would need to trigger a rebuild/redeploy of your Nuxt app whenever content changes are pushed. This is a design choice for performance and consistency in Nuxt Content v3 Nuxt Content v3 Advanced Database. If you need more dynamic content updates, you may need to consider a headless CMS or a different architecture. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------
<@290965653660106762> Kapa.ai is still learning and improving, please let me know how I did by reacting below.
@kapa.ai is it planned to be implemented in a later version? Is it on the roadmap maybe or discussed in GitHub issues?
Let me check the knowledge base for you again. One moment! :books:
----------------------
Based on the available knowledge sources, there is no explicit mention of plans to support live content updates (i.e., re-parsing or re-indexing Markdown files in production without a rebuild/redeploy) in future versions of Nuxt Content. The official roadmap and changelogs for Nuxt Content v3 and Nuxt 4 do not list this feature, nor do they reference any related discussions or GitHub issues about implementing such functionality Nuxt 4 Roadmap Nuxt Content v3 Blog.
The roadmap focuses on other features such as performance improvements, SQL-based storage, Studio integration, and enhanced editing experiences, but does not mention hot content updates in production environments.
If this feature is critical for your workflow, you may want to monitor the Nuxt Content discussions or open a feature request on GitHub, as the current documentation and roadmap do not indicate it is planned.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
<@290965653660106762> Kapa.ai is still learning and improving, please let me know how I did by reacting below.