Launch from GitHub runs pieces of fly launch followed by fly deploy. It can create a pull request with the files produced. So @halfer everything you know about how the CLI works applies here.
When it works, the GitHub UI gets you up and running quickly and effortlessly, so in many cases it is worth trying – why not? That being said, I see this post being flagged as dotnet, I see signalr in the Dockerfile output, and these aren’t areas we have focused on, so it likely will take some experimentation to get it working. I don’t know about others, but in such cases I prefer the CLI.
The one thing that caught my eye was /bin/bash login -c deploy.rb. I don’t know why you would want to be running a login shell as a part of deployment, and I was surprised to see a .rb extension. Any insight as to what is going on here?
From what I can gather, the docker build succeeded, and it was the execution of deploy.rb that failed. This could be a secret that wasn’t set, a database that wasn’t seeded, or any of a number of reasons. Running fly launch or fly deploy will show you some logs, you can get more from the dashboard or by running fly logs.
@Shagrim , if you share your logs, I’m sure somebody here can talk you through it.