Fly Machines still scale to zero after updating fly.toml to min_machines_running to 1

1

Hey there, I had a staging server that I initially set to scale to zero using

min_machines_running  = 0

However I decided I wanted to run this machine without scaling down so I updated my config to

app = "foundry-staging-trpc-web"
primary_region = "lax"

[build]

[http_service]
internal_port = 4007
force_https = true
auto_stop_machines = true
auto_start_machines = true
min_machines_running = 1 // NEW
processes = ["app"]
[http_service.concurrency]
hard_limit = 25
soft_limit = 20
type = "connections"

[[vm]]
cpu_kind = "shared"
cpus = 1
memory_mb = 512

[deploy]
release_command = "../../../scripts/supabase-db-push.sh"

I confirmed that the config was updated by running fly config show --app foundry-staging-trpc-web, which displayed the following

{
  "app": "foundry-staging-trpc-web",
  "primary_region": "lax",
  "deploy": {
    "release_command": "../../../scripts/supabase-db-push.sh"
  },
  "http_service": {
    "internal_port": 4007,
    "force_https": true,
    "auto_stop_machines": true,
    "auto_start_machines": true,
    "min_machines_running": 1,
    "processes": [
      "app"
    ],
    "concurrency": {
      "type": "connections",
      "hard_limit": 25,
      "soft_limit": 20
    }
  },
  "vm": [
    {
      "cpu_kind": "shared",
      "cpus": 1,
      "memory_mb": 512
    }
  ]
}

However after 5 minutes, this server…still changes to the stopped state…what am I doing wrong?

2

Okay…i think i see why, my primary region is LAX but the only machine I have listed is in SJC…weird

3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.