How to not rebuild pages on deployment
Unanswered
Jersey Wooly posted this in #help-forum
Jersey WoolyOP
my site is now has around 2.5k pages and it takes around 5mins to build which is killing me.
the problem is that most pages are static data which never change. say i want to change the color of a button, then all those pages are generated again and again for no reason.
is there a way to deploy my code without having to wait for pages to be generated since they haven't changed?
the problem is that most pages are static data which never change. say i want to change the color of a button, then all those pages are generated again and again for no reason.
is there a way to deploy my code without having to wait for pages to be generated since they haven't changed?
11 Replies
Jersey WoolyOP
i might be mistaken but it doesn't prevent pages from being re built on deploy. this is for creating new pages after the deployment
as in it won't reduce the deployment time
unless you are ignoring build cache or changing root logic, build cache should deal with this.
Jersey WoolyOP
yes. this is not what I am after. isr allows you to add more pages without having to redeploy.
my need is to be able to deploy fast changes to the site (such as changing layouts) without having to wait for all thousands of pages to be built again
my need is to be able to deploy fast changes to the site (such as changing layouts) without having to wait for all thousands of pages to be built again
@DirtyCajunRice | AppDir unless you are ignoring build cache or changing **root** logic, build cache should deal with this.
Jersey WoolyOP
i don't think I do on purpose. what is root logic?
@Jersey Wooly i don't think I do on purpose. what is root logic?
a layout anywhere at or above a dynamic page, or the dynamic page itself.
if you are using generate static params it is not “never changing†because build cache is based on existing files pre-templating.
Jersey WoolyOP
hmm maybe i have messed up there. thanks for the pointers.
will investigate what's happening and report back
will investigate what's happening and report back
Jersey WoolyOP
I had a look and i am not using
generateStaticParams(). is there a way to tell if the cache is used for specific pages or not? i checked on vercel and it it mentions Restored build cache and Uploading build cache [99.51 MB]... Build cache uploaded: 2.974s in the end.