Let’s say I have this start of the file in the fly.toml:
app = 'some-app-name'
primary_region = 'ams'
[build]
dockerfile = 'langgraph.Dockerfile'
[env]
SOME_ENV_VAR = ...
[http_service]
internal_port = 8000
force_https = true
auto_stop_machines = 'stop'
auto_start_machines = true
min_machines_running = 1
processes = ['app']
[[services]]
protocol = 'tcp'
internal_port = 8000
tcp_checks = []
[[services.ports]]
port = 80
handlers = ['http']
[[services.ports]]
port = 443
handlers = ['tls', 'http']
[[vm]]
memory = '2gb'
cpu_kind = 'shared'
cpus = 2
If there is a machine running in the “ams” region, and I switch to “nrt”, if i do fly deploy...
, then the old machine in “ams” will still exist. I have to manually kill the ams machine, the relaunch fly deploy
for the new machine in the new region to come alive.
Is this normal? Do i need to do something as part of my CI/CD pipeline such as shutting down machines? I would think it strange.