You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't host my site on Vercel (at least, not this project), and currently, deployment involves packaging the Next site into a container and deploying via Kubernetes. Currently, that build process involves generating an NGINX container that serves all the static files and a NextJS container doing SSR. It works decently well.
The one issue I have is that it doesn't keep previous builds around, which means that if a user (lets call him Brian) opens the site, I deploy a new version, and then Brian tries to load a code-split (code-splat? what's the past tense here?) piece of the site, it'll fail because the build id is different.
What are others doing? Conceivably, I could upload the builds to a cloud storage bucket and serve from that (so that we don't purge the old builds), but that would just grow in storage space over time (or at least until someone goes and manually clears it).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I don't host my site on Vercel (at least, not this project), and currently, deployment involves packaging the Next site into a container and deploying via Kubernetes. Currently, that build process involves generating an NGINX container that serves all the static files and a NextJS container doing SSR. It works decently well.
The one issue I have is that it doesn't keep previous builds around, which means that if a user (lets call him Brian) opens the site, I deploy a new version, and then Brian tries to load a code-split (code-splat? what's the past tense here?) piece of the site, it'll fail because the build id is different.
What are others doing? Conceivably, I could upload the builds to a cloud storage bucket and serve from that (so that we don't purge the old builds), but that would just grow in storage space over time (or at least until someone goes and manually clears it).
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions