Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project: CloudFlare Pages post-migration #2751

Closed
11 of 14 tasks
larsyencken opened this issue Oct 12, 2023 · 2 comments
Closed
11 of 14 tasks

Project: CloudFlare Pages post-migration #2751

larsyencken opened this issue Oct 12, 2023 · 2 comments

Comments

@larsyencken
Copy link
Contributor

larsyencken commented Oct 12, 2023

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
  • 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
  • Lars will clarify the contract details

Issues

(Marcel to clarify)

Must have

Nice to have

@larsyencken
Copy link
Contributor Author

Just a heads up, Daniel and I are chatting to Netlify tomorrow, we'll clarify anything we need to then.

@marcelgerber
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants