I’m experiencing the same issues as nate - my apps cannot resolve the internal hostname (Phoenix/Elixir app with Ecto); I’ve tried detaching, reattaching (there was a 500 in there also), deleting and recreating the apps to no avail.
Also, yes - the experimental private_network setting is enabled in fly.toml for the app.
Btw, the Postgre instance isn’t exposed outside of the external network, correct (which is the desired behaviour IMHO) - specifically since Fly does not allow exposing ports other than 80, 443, 5000 and 10000-10100? Is that correct?
Also, two unrelated questions, but didn’t want to open a separate topic:
Can we rename running apps? If yes, will attached Postgre instances be affected?
Regarding pricing, the Pricing pages says re/ Free tier
8,436,960 seconds per month / Run 3 shared-cpu-1x VMs full time.
But shared-cpu-1x has three price tiers, based on allocated RAM - so how is that calculated? Does it mean 3 free nodes with 256MB and pro-rated amount of 1GB free nodes (1.09 nodes)? Also, in the developer docs, it is not specified whether fly scale memory accepts an arbitrary amount/megabyte input or only the predefined ones from the pricing page (256, 1024, 2048)?
P.S: Also, to add 2 more cents, I think the default grace_period should be slightly increased, I’d imagine most apps can take a bit to startup (not just talking Elixir, but any)…and from my experience it was not immediately clear that this was causing the failure of the deployment (could be better documented). And also should probably be documented that there seems to be a hard limit of 120s for the grace_period? This becomes noticeable if you do any heavier tasks (or build tasks) as part of the CMD directive in the Dockerfile instead of RUN (despite this being a bit of an anti-pattern, it is quite frequent)