How to update the FLY CTL version Wasp uses
I need to run Wasp deploy fly deploy with the option --depot="false", but it says it's not a valid option.
1 Reply
Hi @Gwain. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
To address your question about updating the Fly CLI version that Wasp uses and the issue with the
--depot="false" option, I don't have enough specific information in the provided knowledge sources to give you a complete answer. However, I can offer some relevant insights based on the available information:
1. Wasp version: First, ensure you're using the latest version of Wasp. You can check your current version by running wasp version and update it if necessary using the following command:
Github Issue: Make process of updating Wasp nicer (https://github.com/wasp-lang/wasp/issues/616)
2. Fly.io deployment: Wasp uses Fly.io for deployment, but the knowledge sources don't provide specific information about updating the Fly CLI version used by Wasp or about the --depot="false" option.
3. Manual deployment: If you need more control over the deployment process, you might consider deploying manually. In this case, you would have more flexibility in using Fly CLI options directly. You can find information about manual deployment in the Wasp documentation on manual deployment (https://wasp-lang.dev/docs/advanced/deployment/manually#redeploying-after-wasp-builds).
4. Checking deployed code: If you're experiencing issues with your deployment, you can inspect the exact code that Fly deploys by looking in the .wasp/build folder. This contains the generated Node.js and React code for your app Discord support thread (https://discord.com/channels/686873244791210014/1223671727943319584).
If you're still facing issues with the Fly CLI options, you might need to consult the Fly.io documentation directly or reach out to the Wasp community for more specific guidance, as the provided knowledge sources don't cover this particular scenario.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Gwain, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?