SSR caching about nextein HOT 3 CLOSED

@laurendorman

The main purpose for nextein is to create a static site. The deployed result should be just static content. I believe that each provider such as zeit or netlify would have a way to set the required HTTP headers for that matter.

Now, in case you want to deploy a non exported version, which in theory you can do it, maybe I can add some hooks (like copying the example from next example and enable SSR cache by using a config option). I'm just not sure what are the possible issues with deploying a non exported version since the custom server implemented in nextein is purely made to support dev mode and HMR.

Some references from Netlify:
https://www.netlify.com/blog/2017/02/23/better-living-through-caching/
https://www.netlify.com/docs/headers-and-basic-auth/#custom-headers

from nextein.

@elmasse, I am using Zeit for hosting and it looks like the only way to do this properly is with a custom server, with the use of a CDN, or possibly writing some middleware. I will look into my options to see what makes the most sense for this project.

Thanks for the response and clarity!

Cheers.

from nextein.

@laurendorman if you are deploying a static site in now.sh all assets (except the index.html) are cached. Check this screenshot from the nextein.now.sh deploy:

This includes not only the assets in the static folder such as images but also all .js files generated by next.

The SSR cache in this case is useless since this is a static deploy and there is no server generating content.

Hope this helps!

from nextein.