I’m making this blog using nuxt lately. I built it at local machine and deployed it GitHub Pages, using push-dir until now. But building at local machine is troublesome, and I’ll edit a bit on GitHub directly, I considered to use CD sevice. I thought that Circle CI is good, but Netlify has the CD mechanism, can use own domain, and it’s free! So, I have been moved to Netlify this blog.
npm run generategenerate static files to
distdirectory whole, that’s all.
It’s very easy. Maybe you can do it with only smartphone! :thumbsup:
I achieved the original goals that automatic deployment.
Audits score is no change to compare with GitHub Pages. (It’s natural that this blog is very few CSS :stuck_out_tongue_closed_eyes: )
max-age=0, must-revalidate, public
must-revalidate is a directive that:
Netlify server set ETag and
Cache-control: max-age=0 automatically.
It means, browser always check whether content has been changed and use cache while that is no change.
Is it too slow that always request content? Netlify’s blog said:
The CDN makes the check-in from the browser fast - it talks with the node closest to it and that node is ready with an instant answer as to whether the content is usable as-is (Etag matches, no deploys or rollbacks have happened). Using HTTP/2, browsers multiplexes these connections so they can all happen within a single connection and you don’t have to do things like negotiate the HTTPS handshake over and over again.
However this blog has filename based cache-busting JS and CSS, so I thought their content should edit Cache-Control max-age and I tried that. But… this blog is already cached by service worker, so it did not make sense :joy: