Hi! I am currently investigating a bug in our CI workflow, where I spin up a temporary pocketbase db instance for each branch. This db has no persistent volume attached.
Lately (since we migrated to machines, perhaps?) I have experienced a bug where our e2e-tests sometimes fails and I suspect that the following (from docs) is the problem:
fly deploycreates two Machines per process, for resilience purposes.”
It sounds like something that may cause havoc since it is 50/50 that the “right” machine is used. It is a hypothesis at least.
I don’t see any options in
fly.toml for configuring this. Is there such? If not, can you add it? It is not always the case that you want a resilient setup if it adds complexity and cost. I just one app running in one machine.
Furthermore, the docs says
"When Machines are created or destroyed using either of the above methods, the resulting scale is preserved by
fly deploy—except in the case that you scale right down to zero Machines. In that case,
fly deployseeds the app with new Machines according to the
What does it mean “according to
primary_region”? Can I control the scale with that field?
fra(1) ? If I use
fly scale count 1, will that option be saved? Where?
Please enlighten me!