I’m trying to launch my node app and it seems to be stuck in the same place each time I try and deploy it
Update available 0.0.316 -> v0.0.333.
Run "flyctl version update" to upgrade.
An existing fly.toml file was found for app divine-sun-6758
App is not running, deploy...
==> Validating app configuration
--> Validating app configuration done
TCP 80/443 ⇢ 8080
Remote builder fly-builder-wild-shape-805 ready
==> Building image with Buildpacks
--> docker host: 20.10.12 linux x86_64
20: Pulling from heroku/buildpacks
Status: Image is up to date for heroku/buildpacks:20
20-cnb: Pulling from heroku/heroku
Status: Image is up to date for heroku/heroku:20-cnb
that was it. I didn’t have a .dockerignore so created one an added node_modules. I’m new to Fly and this feels like a newbie issue. I’m wondering if it might be helpful if Flyctl was enhanced to be smart enough to detect / handle this common case?
OK, the next problem I have is the app is not accessible externally. I can flyctl ssh console and do a curl localhost:8080 and it works. but I can’t access it remotely and also during the deploy the health check fails.