`release_command` is run with customizable vm memory

The release_command is handy to run migration but it runs on the largest machine based on the default process group. I wonder whether it’s possible to allow me to customize the vm memory size. My migration tool (prisma) requires more memory usage than my app running.

The temporary Machine inherits the size from the largest Machine in the default process group of the app as of flyctl v0.0.508 (they also default larger on empty/new apps, using the Machine shared-cpu-2x preset).

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