Revalidate CMS data vs. Deploy Hook
Unanswered
Braque du Bourbonnais posted this in #help-forum
Braque du BourbonnaisOP
I have a Next.js front-end consuming data from a CMS. To get data from the CMS, I'm calling
This whole time, I thought I still needed to rebuild and deploy my site whenever content in the CMS changed. I have a button in the CMS linked to a Deploy Hook on my repo so that my client can rebuild and deploy the site. However, I noticed that as long as I call
I'm clearly misunderstanding something about the SSR, Server Component, and/or data cache architecture. Do I not need to rebuild for CMS content changes?
fetch inside Server Components with tags: ['cms'] in the fetch options.This whole time, I thought I still needed to rebuild and deploy my site whenever content in the CMS changed. I have a button in the CMS linked to a Deploy Hook on my repo so that my client can rebuild and deploy the site. However, I noticed that as long as I call
revalidateTag('cms'), the next refresh of my page has the latest data, no rebuild required.I'm clearly misunderstanding something about the SSR, Server Component, and/or data cache architecture. Do I not need to rebuild for CMS content changes?