Had to cancel subscription for #Netlify Analytics on https://nho.link because it doesn't support redirects yet, it was almost useless.
But I wanted to pay for the global Netlify service I use for other sites, so I subscribed for Analytics for another site that already have Google Analytics, let's see how they compare.
I still don't understand why using Cloudflare in front of Netlify allows for a much better and stable Time To First Byte (TTFB) than Cloudflare Pages or Netlify alone… 🤷♂️
TTFB for static sites should always be very low.
I'm still looking for an alternative to Forestry:
https://forestry.io/blog/tina-cloud-the-next-forestry/
As Netlify doesn't seem to care for Netlify CMS anymore:
https://answers.netlify.com/t/is-this-project-dead/70988/1
A fork managed by a community might be a good solution, I'll keep an eye on it:
https://staticjscms.netlify.app/
Any idea why there's so much TTFB difference on #Netlify for main vs branch deploys?
Here is TTFB for:
If you want to run a #GitHub Action after a #Cloudflare Pages build is done, you can use @WalshyDev's Action: https://github.com/marketplace/actions/cloudflare-pages-await
I hope Cloudflare Pages will get triggers like #Netlify: https://docs.netlify.com/functions/trigger-on-events/
You may have this issue with Node 16.5.1 on #Netlify: This setting is no longer used. npm stores temporary files in a special location in the cache…
Quick fix: put 16.5.0 in an .nvmrc file