And one could specify a dockerfile (if there isn’t one named Dockerfile in your project’s root) with flyctl’s --dockerfile /path/to/dockerfile switch (ref).
The first edit looks to be missing the checkout step so the GitHub runner wouldn’t have access to your source files. Not positive that will resolve your whole issue but we may learn more!
I think I ALMSOT got it , the fly.toml that i was getting from there was missing the build step maybe because i use the auto import from heroku . so i deleted that file and use the command you told me , but now i think there are parts missing for example i sue playwright and now im getting the following error :
on heroku i used a package that allowed me to use it , but i dont know how to do it here on fly.io , the auto importer did it right because playwright was working .
So que question would be how can I get the fly.toml that was generated with the auto importer ?
I used Turboku and i dont have access to the docker file or the fly.toml auto generated , they were not added into my repo, is there a way to obtain them . so i can integrate my github action ?
Turboku actually pulls your prebuilt app down from Heroku (it’s basically a docker image), then deploys that. It doesn’t run through the fly launch process or create a Dockerfile for you.
now is not even redeploying after the deploy on heroku was made (I have being waiting more than an hour ,the first time it worked as you can see on the screenshot )
