I have existing fly.toml and I want to launch app with this settings and app name.
It ask me: Would you like to copy its configuration to the new app? Yes
but it is not working, new fly.toml is created.
I have existing fly.toml and I want to launch app with this settings and app name.
It ask me: Would you like to copy its configuration to the new app? Yes
but it is not working, new fly.toml is created.
flyctl launch
always tries to create a new app. Since you already have a config, you can first create an app with flyctl apps create <app-name> --no-config
then deploy with flyctl deploy
which will leave the config file alone.
Reusing configs is clunky right now, especially with flyctl launch
. Creating an app if it doesn’t exist makes sense though.
The --no-config doesn’t exists. It worked without it.
When deploying, If you have a config file name different than fly.toml, use:
fly deploy -c your-config-file.toml