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
We have just migrated our site from Netlify to CloudFlare Pages, in order to reduce costs, kill tech debt, and lean more into CloudFlare's awesome ecosystem.
Goal / this cycle
Clean up our migration and ensure that when the Netlify contract ends we are fine. Remove Netlify code from our stack.
Rabbit holes / open questions
Small sites - NICE TO HAVE
We have small sites that we keep on Netlify, do we need to migrate them too?
We believe that small sites are going to be fine on our free Netlify plan
Provided we can verify that, we can probably leave them
Netlify functions - IN SCOPE
We have two Netlify functions that need migrating to CloudFlare (donations & feedback)
We have agreed that they are in scope
Old staging servers - OUT OF SCOPE
We have old staging servers that use Netlify
We would tear them down, but they are the only ones that have a running Wordpress admin
For that reason, we'll leave them unless we can get the Wordpress admin working on new staging servers
That's beyond the scope of this cycle
Post-contract Netlify plan - LARS TO CLARIFY
We need to understand more clearly what our Netlify situation will look like after our contract ends
This is now done, and we're almost fully off of Netlify.
The one exception is that the owid-donate Netlify function is still running on Netlify. This decision was based on the assumption that the function would be deprecated after the donor page redesign, but with changes in that project it now looks like v1 of the donor page redesign will still rely on a worker of some sort. So, it might be worth reconsidering this in the future.
I plan to work on #2502 next week (waiting for some feedback from Natasha), which would then mean that almost all of the things on this ticket got finished.
Background
We have just migrated our site from Netlify to CloudFlare Pages, in order to reduce costs, kill tech debt, and lean more into CloudFlare's awesome ecosystem.
Goal / this cycle
Clean up our migration and ensure that when the Netlify contract ends we are fine. Remove Netlify code from our stack.
Rabbit holes / open questions
Small sites - NICE TO HAVE
Netlify functions - IN SCOPE
Old staging servers - OUT OF SCOPE
Post-contract Netlify plan - LARS TO CLARIFY
Issues
(Marcel to clarify)
Must have
Nice to have
owid-static
againThe text was updated successfully, but these errors were encountered: