Remove/destroy Wasp Fly.io deployment
I created a simple Wasp app and tested deploying it to Fly.io and it all worked great. As it was just a silly experiment, I'd like to now take down (decommission) the deployment. Is this something I can do through the Wasp CLI, or do I need to use the fly cli directly to do this? Any guidance would be greatly appreciated. Thanks!
3 Replies
Hi @tomhh. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Currently, the Wasp CLI does not provide a built-in command to remove or destroy a Fly.io deployment. To decommission your Wasp app from Fly.io, you will need to use the Fly.io CLI (flyctl) directly.
The recommended approach is:
1. Identify the names of the apps you want to destroy. Wasp typically creates three apps on Fly.io for a project:
-
You can confirm these in your Fly.io dashboard or from the TOML files generated in your project root (
-
<your-app-name>-client
- <your-app-name>-server
- <your-app-name>-db
You can confirm these in your Fly.io dashboard or from the TOML files generated in your project root (
fly-server.toml
, fly-client.toml
) Deploying with the Wasp CLI > Deploying.
2. Use the Fly.io CLI to destroy each app:
For example:
This will remove the deployed resources from your Fly.io account Set Up a Fly.io App.
If you encounter issues (e.g., Fly not allowing you to create new apps with the same name in the future), destroying the old apps as above is the recommended solution.
In summary: use the Fly.io CLI (flyctl) to destroy your Wasp app deployments, as Wasp CLI does not currently support this operation directly.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @tomhh, 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?I'll report back once I've tested this to confirm if the instructions work as expected
Hey @tomhh. Yes, the bot is right 🙂
We do not provide a way to do this through the Wasp CLI. Do you think it makes sense we do?