Update fly_io deployments

[ehmatthes]

• [ ] Integration test without automate-all fails. Complains that a fly app has not yet been created, even though one has.
• [ ] Integration test with automat all fails. Complains about not recognizing a region.

[ehmatthes]

Non-automate-all run

% fly apps create --generate-name
automatically selected personal organization: Eric Matthes
New app created: lingering-fog-2361
(b_env) eric@Erics-Mac-Studio django-simple-deploy-dev-project_18244 % python manage.py simple_deploy --platform fly_io
Configuring project for deployment...
  Deployment target: fly_io

***** Deployments to Fly.io are experimental at this point ***

- Support for deploying to Fly.io is in an exploratory phase at this point.
- You should only be using this project to deploy to Fly.io at this point if
  you are interested in helping to develop or test the simple_deploy project.
- You should look at the deploy_flyio.py script before running this command,
  so you know what kinds of changes will be made to your project.
- This command will likely fail if you run it more than once.
- This command may not work if you already have a project deployed to Fly.io.
- You should understand the Fly.io console, and be comfortable deleting resources
  that are created during this deployment.
- You may want to cancel this run and deploy to a different platform.

Are you sure you want to do this? (yes|no) 
yes
  Continuing with Fly.io deployment...
  Found .git dir at /Users/eric/projects/django-simple-deploy-dev-project_18244.
  Dependency management system: req_txt
  Checking current project requirements...
    Found existing dependencies:
      asgiref
      certifi
      charset-normalizer
      Django
      django-bootstrap5
      idna
      requests
      sqlparse
      urllib3

Looking for Fly.io app to deploy against...
CommandError: 
A Fly.io app name could not be found.

The simple_deploy command expects that you've already created an app on Fly.io
to push to.

If you haven't done so, run the following command to create a new Fly.io app:

    $ flyctl apps create --generate-name

Then run simple_deploy again.

[ehmatthes]

• [ ] Main stability issue with fly is determining which app the user just created.
• [ ] Can list apps that were identified, and prompt user for which one to deploy to.

[ehmatthes]

Failing deployment because it wants to create 2 "app" machines:

--> Pushing image done
image: registry.fly.io/white-glade-5822:deployment-01H3ANTSW6XD3ZGHKCG3PPZ2MF
image size: 169 MB

Watch your app at https://fly.io/apps/white-glade-5822/monitoring

Provisioning ips for white-glade-5822
  Dedicated ipv6: 2a09:8280:1::5b:2f09
  Shared ipv4: 66.241.124.144
  Add a dedicated ipv4 with: fly ips allocate-v4
Running white-glade-5822 release_command: python manage.py migrate
  release_command 3d8d312c215689 completed successfully
This deployment will:
 * create 2 "app" machines

No machines in group app, launching a new machine
Error: error creating a new machine: failed to launch VM: To create more than 1 machine per app please add a payment method. https://fly.io/dashboard/eric-matthes/billing
Please note that release commands run in their own ephemeral machine, and therefore count towards the machine limit.

• [ ] Why is it needing multiple machines?
• [x] Does adding payment method fix this?
• [ ] What does this mean for trial users?

[ehmatthes]

[ehmatthes]

• Payment method fixed the issue.
• Is this issue from a change in ie Hobby level?
  • Maybe I'm provisioning a resource that's no longer free?

[ehmatthes]

Closing for newer, more specific issues.