Automatically applying D1 migrations when deploying pages
I've found a few topics on this, but they've sadly gone unanswered. What is the expected route for applying migrations to a bound D1 database when deploying?
I'd sort of expected this to 'just work' via the built in git integration (since almost everything else does) and my config is vanilla, but that doesn't seem to be the case.
It looks I need to create a CI/CD flow, avoiding the use of the built in git connection entirely and applying there. Though I can't see any docs pointing in that direction.
Is that correct, or am I missing something? All the docs I can find describe applying migrations manually, but that's not appropriate after the initial playing around stage. It would be an absolute dream if I could just use CloudFlare's native deploys.
I'd sort of expected this to 'just work' via the built in git integration (since almost everything else does) and my config is vanilla, but that doesn't seem to be the case.
It looks I need to create a CI/CD flow, avoiding the use of the built in git connection entirely and applying there. Though I can't see any docs pointing in that direction.
Is that correct, or am I missing something? All the docs I can find describe applying migrations manually, but that's not appropriate after the initial playing around stage. It would be an absolute dream if I could just use CloudFlare's native deploys.
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
86,529Members
Resources
Similar Threads
Was this page helpful?
