Hello! I’d like to switch the region which my app will be running from-- Seattle to Chicago.
Is it enough to simply change the primary_region variable in fly.toml on next deployment?
It’s a Golang app with persistent SQLite on its own volume.
I believe this will cause downtime since the rolling update is primarily done in the same region (could be wrong.) It’s safer to fly scale count 1 --region ord, then once that’s good, scale down the one in seattle. Then u can update your toml file.
1 Like
Thank you!
This did the trick, but of course wiped my DB because scaling via fly scale of course didn’t copy over the contents of my SQLite volume. This is not a problem luckily, as I’m not in prod yet.
Consider using LiteFS or Turso for distributed sqlite. You’ll still have the sqlite volume issue if you scale up or to another region.
1 Like
I am well aware! There’s also Marmot. I might actually do this anyways. The thing is, I am using Pocketbase and so its hooks are unusable if you use those solutions. But I’m not using the hooks anyways so I might try out LiteFS.
I am assuming that adding a LIteFS node would double my monthly charges though, right?
I’m not sure of the pricing implications.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.