Replies: 1 comment
-
So it looks like the ability to do this was remove just prior to |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Great tool! Like others, I'm using it to synchronize pages between multiple NextJS frontends running in different containers.
My question has to do with the build process. I understand that I can have generated pages cached during build. However, currently my Redis instance is private inside our cloud and I'd prefer that it stay that way. The problem is that, as a result, we pay the page build penalty twice: first during build (non user-facing), and then during the first page load (user facing). I'd prefer to just pay the first penalty.
However, our NextJS containers ship with all the built pages in the
server/pages
directory. Is there a way to load these values to prepopulate the cache when the server starts? The file timestamps could be used to set an insert time, assuming that's possible with Redis. That would support building into the cache in a way that didn't require exposing the Redis instance used to cache values.Beta Was this translation helpful? Give feedback.
All reactions