We have to decide if this is wanted behaviour or not. I'd propose printing an error and stopping the command when there's already a fly.toml file present, or perhaps ask if the user just wants to deploy instead? Curious to see what you guys think.
We can do both, Print out an error message saying a fly.toml exists so we cant do a launch, and prompt if the user want to deploy instead, then if the answer is yes. the cli deploys
We have to decide if this is wanted behaviour or not. I'd propose printing an error and stopping the command when there's already a fly.toml file present, or perhaps ask if the user just wants to deploy instead? Curious to see what you guys think.