Resolve region issue with Fly deployments

[ehmatthes]

See #255, #220.

• [x] Look at updated fly CLI version?
• [x] Consider hardcoding a known region that works, and then coding a reliable solution that picks region closest to user.
• [x] Complete other tasks that arose during this fix.
  • [x] Fix failing unit tests. #257
• [x] Consider making a release so that PyPI version has preliminary support for Fly again.
• [x] Test against PyPI version; document command in official docs.
  • [x] automate all run
  • [x] configuration only run (it is using 0.5.16)
• [x] Update changelog to have space for unreleased changes.
• [ ] Delete branches.

[ehmatthes]

Working notes

• I did some work on this over the summer; it's defaulting to sea if a region is not found.
• On PyPI, that's not happening.
• I would guess that #255 would be resolved through:
  • $ pip install 'django-simple-deploy @ https://github.com/ehmatthes/django-simple-deploy
• The root issue is deprecation of the fly apps region command for most V2 apps.
• Using build_dev_env.py, adding docs for that.
• Integration tests should pass for me on this dev branch, but fail against the PyPI version:
  • [x] Passes on dev branch.
    • [x] fly open is deprecated, replace with fly apps open: fly open output: Command "open" is deprecated, [use](https://fly.io/docs/flyctl/apps-open/)fly apps openinstead
    • [x] Update fly open call in test script.
    • [x] Update fly open in --automate-all script.
    • [ ] Deployment is failing through integration test; run deployment through test, then go to test project dir and try to troubleshoot from there. Worked on first fly deploy call; that indicates a flakiness on Fly's part, not an issue from simple_deploy?
  • [ ] Fails against PyPI.
  • [x] Document testing against PyPI on official integration tests doc page.

[ehmatthes]

Sort discrepancy between integration test and manual run

When I run the integration test, it's failing at the fly deploy call. When I hop into the artifact project, fly deploy works.

• [x] Manual run makes it easy to see some output, ie that 'sea' is going to be used for region; could cancel run, modify _get_region(), and see if we can pull up the correct region. Find the right command in the cli to get the region.

[ehmatthes]

About regions

• fly regions -a is deprecated.
• fly platform regions just gives a list of possible regions; no help here.
• "Discovering your Application's Region" src
  • "You can see which regions your app is running in with fly status." Doesn't work for an app that's been created but not deployed.
  • Could present choice of regions.
  • [ ] Should probably be passing --json to all fly calls where we need to parse output. #259

Current solution, taken from _get_region():

- This forum post: https://community.fly.io/t/feature-requests-region-latency-tests/968/6
- Leads to this tool: https://liveview-counter.fly.dev/
- It identifies the region with lowest latency, ie "Connected to iad".
- Solution: request this page, parse for that phrase, select region.
- Return 'sea' if this doesn't work.

[ehmatthes]

Update automate_all

---

• [x] Run integration test against --automate-all; should fail.
  • [x] Passed; for some reason fly open is still working. I don't trust it to remain available, so updated simple_deploy to use fly apps open -a {app_name}. This required setting self.app_name in fly_io.deploy.py.
• [x] Update fly open call.
• [x] Run integration test again; should pass.
  • [x] automate all
  • [x] configuration only

[ehmatthes]

It feels good to have a new release out! I'll delete branches later.