So we’ve done this now:
# fly.toml file generated for pdp-preview-db on 2023-01-18T10:53:32-05:00
app = "pdp-preview-db"
kill_signal = "SIGINT"
kill_timeout = 5
processes = []
[env]
[experimental]
auto_rollback = true
[[services]]
http_checks = []
internal_port = 8080
processes = ["app"]
protocol = "tcp"
script_checks = []
[services.concurrency]
hard_limit = 100
soft_limit = 75
type = "connections"
[[services.ports]]
force_https = true
handlers = ["http"]
port = 80
[[services.ports]]
handlers = ["tls", "http"]
port = 443
[[services.tcp_checks]]
grace_period = "1s"
interval = "15s"
restart_limit = 0
timeout = "2s"
❯ fly deploy . --app pdp-preview-db --image flyio/postgres:14.4
==> Verifying app config
--> Verified app config
==> Building image
Searching for image 'flyio/postgres:14.4' remotely...
image found: img_wd57v5wx3k7v38o0
? This feature is highly experimental and may produce unexpected results. Proceed? Yes
Deploying with rolling strategy ✓
But the result is that concurrency is NOT updated. Why?
❯ f config show -a pdp-preview-db
{
"env": {},
"experimental": {
"auto_rollback": true
},
"kill_signal": "SIGINT",
"kill_timeout": 5,
"processes": [],
"services": [
{
"concurrency": {
"hard_limit": 25,
"soft_limit": 20,
"type": "connections"
},
"http_checks": [],
"internal_port": 8080,
"ports": [
{
"force_https": true,
"handlers": [
"http"
],
"port": 80
},
{
"handlers": [
"tls",
"http"
],
"port": 443
}
],
"processes": [
"app"
],
"protocol": "tcp",
"script_checks": [],
"tcp_checks": [
{
"grace_period": "1s",
"interval": "15s",
"restart_limit": 0,
"timeout": "2s"
}
]
}
]
}