What's the best way to run fly deploy with arguments?
I'm trying to run
wasp deploy fly deploy --depot=false to work around an issue with flyctl depot https://community.fly.io/t/hanging-on-waiting-for-depot-builder/23674
When I run fly alone i get other errors which tells me i'm missing somehting:
Fly.io
Hanging on Waiting for depot builder...
These deploys have worked for weeks now, suddenly not working: ==> Verifying app config Validating fly.toml ✓ Configuration is valid --> Verified app config ==> Building image Waiting for depot builder... WARN failed to finish build in graphql: Post "https://api.fly.io/graphql": context canceled The last line shows after I ctrl-c the build. E...
12 Replies
Hi @Noah. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
To run
fly deploy with arguments using Wasp's deployment CLI, you can use the wasp deploy fly cmd command. This allows you to run arbitrary Fly commands with additional arguments. Here's how you can do it:
This command will run fly deploy with the --depot=false argument for your server app. The --context server part is important as it specifies that the command should be run for the server app.
However, it's important to note that the error you're encountering when running fly deploy directly suggests that there might be some configuration issues with your Fly.io setup. The Wasp CLI handles a lot of the configuration automatically, which is why you're seeing different behavior when using fly directly versus wasp deploy fly deploy.
If you're having issues with the Wasp deployment process, you might want to try the following steps:
1. Ensure you've run wasp deploy fly setup and wasp deploy fly create-db before attempting to deploy.
2. Make sure you have the fly-server.toml and fly-client.toml files in your project root directory. These are created by the Wasp CLI and are necessary for deployment.
3. If you need to customize the deployment process, you can edit these TOML files.
For more detailed information on deploying with the Wasp CLI, you can refer to the Deploying with the Wasp CLI documentation.
If you continue to encounter issues, it might be helpful to review the full deployment process and ensure all steps have been completed correctly. The Deploying Manually guide provides a good overview of the steps involved in deploying a Wasp app, which might help in troubleshooting.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Noah, 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 get this error still, what am i missing
Error: failed to fetch an image or build from source: app does not have a Dockerfile or buildpacks configured. See https://fly.io/docs/reference/configuration/#the-build-section
@kapa.ai
Let me check the knowledge base for you again. One moment! :books:
Sorry @Noah, 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 get this error still, what am i missing
Error: failed to fetch an image or build from source: app does not have a Dockerfile or buildpacks configured. See https://fly.io/docs/reference/configuration/#the-build-section
@kapa.ai
Let me check the knowledge base for you again. One moment! :books:
----------------------
Based on the error message you're seeing, it appears that you're still trying to run
fly deploy directly instead of using the Wasp CLI for deployment. When deploying a Wasp app to Fly.io, it's important to use the Wasp CLI as it handles many configuration details automatically.
Here's what you might be missing:
1. Make sure you're in your Wasp project root directory (where your main.wasp file is located).
2. Instead of running fly deploy directly, use the Wasp CLI command:
This command will use the correct configuration and Dockerfile that Wasp generates for your app.
3. If you need to add the --depot=false flag, you can use the cmd subcommand as mentioned earlier:
4. Ensure that you've run the setup commands before attempting to deploy:
These commands create the necessary configuration files (fly-server.toml and fly-client.toml) in your project root as mentioned in the Wasp documentation.
5. Check that the fly-server.toml and fly-client.toml files exist in your project root. These files are crucial for the deployment process.
If you've followed these steps and are still encountering issues, it might be helpful to review the Deploying with the Wasp CLI documentation for a complete overview of the process.
Remember, when using Wasp, it's important to use the Wasp CLI commands for deployment rather than direct fly commands, as Wasp handles much of the configuration and build process for you.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Noah, 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?@Noah have you figured this one out? Could you share what were you doing?
Fly depot continued to break so I switched to railway 🤷♂️
[email protected] last time they moved my builder to another region because it was unable to start (around 30min)
How's Railway working out for you? More stable?
It's been great, really enjoying it
Nice. Fly is great (and cheaper I think) but lately they have some issues. Railway seems to be a bit more stable at times.