I need to increase fly VM size
How can i increase my fly VM Size?
I want to use wasp deploy, and i know the OG fly command is I think anyways.
i thought i could do it with
but --remote-only isnt an option error.
The root error im getting is
Hence why i want to increase the size.
2 Replies
Hi @Zuck. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the knowledge sources provided, I don't have specific information about increasing the VM size using the
wasp deploy command. However, I can provide some relevant information and suggestions:
1. Memory issues: The error you're encountering ("JavaScript heap out of memory") is similar to an issue mentioned in the knowledge sources where Wasp apps required more memory to run. This was resolved by switching to Vite, which reduced memory usage from 1GB to 200-300MB Github Issue (https://github.com/wasp-lang/wasp/issues/955).
2. Wasp CLI deployment: The Wasp CLI does support deployment to Fly.io, but the documentation doesn't mention specific options for VM size configuration Deploying with the Wasp CLI (https://wasp-lang.dev/docs/advanced/deployment/cli#flyio).
3. Building locally: While not directly related to VM size, the Wasp CLI does support a --build-locally option for wasp deploy fly launch or wasp deploy fly deploy Building Locally (https://wasp-lang.dev/docs/advanced/deployment/cli#building-locally). This might be relevant if you're trying to use --remote-only.
4. Manual deployment: If you need more control over the deployment process, you might consider deploying manually. The Wasp documentation provides steps for manual deployment to Fly.io Fly.io (server and database) (https://wasp-lang.dev/docs/advanced/deployment/manually#flyio-server-and-database).
Given that the Wasp CLI doesn't seem to directly support VM size configuration based on the provided information, you might need to:
1. Deploy manually using Fly.io's CLI to have more control over VM size.
2. Check if there's a way to modify the fly.toml file to include VM size configuration before deploying with Wasp.
3. Reach out to the Wasp community or maintainers for more specific guidance on increasing VM size when using wasp deploy.
If you continue to face issues, it might be helpful to share your problem in the Wasp Discord community or open an issue on the Wasp GitHub repository for more tailored assistance.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Zuck, 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?You can directly use the
fly CLI to do this, it should be fine.
This is how I did it:
And you find your server app name in the toml file 🙂