---------------------- To deploy your Wasp app on Fly.io, you can use the Wasp CLI's `setup` command. This command creates your client and server apps on Fly.io and adds some secrets, but it does not deploy them. The command is as follows: ```bash wasp deploy fly setup ``` The `` is the name of your app and `` is the region where your app will be deployed. You can find the available regions **here** (). After running `setup`, Wasp creates two new files in your project root directory: `fly-server.toml` and `fly-client.toml`. You should include these files in your version control. You can edit these files to further configure your Fly deployments. If you want to maintain multiple apps (for example, for different environments like production, staging, and development), you can add the `--fly-toml-dir ` option to point to different directories. ```bash wasp deploy fly setup --fly-toml-dir ``` Remember to only run `setup` once per app. If you run it multiple times, it will create unnecessary apps on Fly. For deploying the app, you can use the `launch` command which runs `setup`, `create-db`, and `deploy` in sequence. ```bash wasp deploy fly launch ``` If your app requires any other environment variables, you can set them with the `--server-secret` option: ```bash wasp deploy fly launch my-wasp-app mia --server-secret GOOGLE_CLIENT_ID=<...> --server-secret GOOGLE_CLIENT_SECRET=<...> ``` Please refer to the **Wasp CLI documentation** () for more details. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

deploy in fly.io with multiple environment

Similar Threads