The last time I touched this app, I did fly autoscale set balanced min=1 max=4 and it worked. Now it scales in to zero, which has not been a pleasant surprise. Is there a way I can set the new min_machines_running without rebuilding the image? If I edit fly.toml and do fly deploy, my image gets rebuilt. Do I have to specify the last image from the releases, or is there some way to set this configuration with fly machines/app/etc or some replacement for the old autoscale command?
Why is it an issue if your image is rebuilt?
I mean I don’t have the same machine or cache anymore and I’m not completely certain it will build correctly. I wish it wasn’t so, but it still feels weird to me that there’s no migration path for the autoscale command.
This does work. If you put…
$ fly deploy --image registry.fly.io/your-app-name:deployment-<long-base64-ish-string>
…then you need only fly.toml.
(I’ve done this several times, from a local machine that had neither the Dockerfile nor the application’s Elixir source code.)
I agree with @pb30’s overall sentiment, though, that the Fly platform generally does expect you to occasionally rebuild things…
Added appsv2, autoscaling, machines
Yeah, understand you’re pretty far outside the normal use case here. It’s kind of assumed you have your app’s code available and working. How are you going to fix a bug or make any other change?
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.