Hey folks, I had a pretty rough dev experience with using durable objects, and it would be nice to g
Hey folks, I had a pretty rough dev experience with using durable objects, and it would be nice to get some guidance on best practices.
In a dev branch, i set up my Toml file to have a durable object binding without an env (as per docs), but it looked like when i ran wrangler dev —remote, it created a durable object in prod.
That caused a lot of problems, and a separate branch that wasn’t related was unable to deploy bc it didn’t have the migration to delete the durable object.
Also, it looked like deploying to remote dev would update the durable object in prod.
As an example, I don’t really have a good idea of the dev lifecycle. Like if I create a DO for the first time, what should my toml file look like to test & deploy? And after several iterations, what would it look like (e.g. do I need to delete migrations after every deploy?)
In a dev branch, i set up my Toml file to have a durable object binding without an env (as per docs), but it looked like when i ran wrangler dev —remote, it created a durable object in prod.
That caused a lot of problems, and a separate branch that wasn’t related was unable to deploy bc it didn’t have the migration to delete the durable object.
Also, it looked like deploying to remote dev would update the durable object in prod.
As an example, I don’t really have a good idea of the dev lifecycle. Like if I create a DO for the first time, what should my toml file look like to test & deploy? And after several iterations, what would it look like (e.g. do I need to delete migrations after every deploy?)
