No region defined in the fly deploy command, causes deployment to crash about indie-stack

[hilja]

I struggled with region issues a lot, but managed to solve it with help from fly community. Turns out I was just overcomplicating things myself.

You don’t need to set the FLY_REGION or PRIMARY_REGION or --region=<region>, just define primary_region = "<region>" in your fly.toml and let fly set those env vars.

This could be documented better though :)

[hilja]

@MichaelDeBoey Either setting primary_region in fly.toml or using the simplified deployment strategy removed this issue.

[jvazquez441]

I got the same issue with the regions following the README tutorial. I applied the primary_region in the fly.toml file and all worked perfectly when redeployed. Definitely this need to be added or mentioned on the indie-stack README.

[MichaelDeBoey]

@hilja Will this be fixed if you apply the same changes as I did in #225?

[korzewski]

I had the same issue today. Was able to solve it by adding primary_region to fly.toml

kill_signal = "SIGINT"
kill_timeout = 5
processes = [ ]
primary_region = "waw" // <-- this line

[experimental]
allowed_public_ports = [ ]

Github actions was marked as crashed, due to:

Error: timeout reached waiting for healthchecks to pass for machine...

But when I checked it on fly.io, it actually seems to work as expected. After re-run, it's deployed properly (green)

[MichaelDeBoey]

using the simplified deployment strategy

@hilja Can you elaborate on what you mean by that?

[hilja]

@MichaelDeBoey Referring to this PR #225

[MichaelDeBoey]

@hilja Since we're now using that simplified deployment strategy out of the box, I'm going to close this PR

[nicolasrenon]

I know this issue has been closed, but AFAIK the PR mentioned above did not fix the problem.
I'm using the latest version of the stack and I ran into the exact same failure in Github Actions > Deploy.

Not sure why, it seems like it expected dfw region in my case. When running the fly volumes create command, fly asks what region we want for the volume (I picked lax). Either the fly.toml needs to include primary_region or there should be some additional documentation on the README about this.

[adamklingbaum]

I know this issue has been closed, but AFAIK the PR mentioned above did not fix the problem. I'm using the latest version of the stack and I ran into the exact same failure in Github Actions > Deploy.

Not sure why, it seems like it expected dfw region in my case. When running the fly volumes create command, fly asks what region we want for the volume (I picked lax). Either the fly.toml needs to include primary_region or there should be some additional documentation on the README about this.

Same issue for me.