I don't use any build packs in Heroku? Since a while back Heroku just recognizes the Node project and automatically works with it, no need for any extra file.
Or do you mean it's the same in Fly.io? If it auto-detects Node.js (through package.json), or at most allows for a dropdown to say "Node.js project", then that sounds about right for me.
At this point, flyctl creates an app for you and writes your configuration to a fly.toml file. You'll then be prompted to build and deploy your app. Once complete, your app will be running on fly.
Well it still creates a fly.toml for you, which is still a new config file that I have to maintain across projects.
You update the toml file once (e.g if you have a release step), and then don't touch it again. Its more powerful than Heroku, so with that it gives you the option of adding additional config options.
I mean it even creates the basic file for you, I'm not sure what the issue is?
Comments
I don't use any build packs in Heroku? Since a while back Heroku just recognizes the Node project and automatically works with it, no need for any extra file.
Or do you mean it's the same in Fly.io? If it auto-detects Node.js (through package.json), or at most allows for a dropdown to say "Node.js project", then that sounds about right for me.
Indeed the docs[1] say Fly automatically detects a Node.js project, so you don't need to create a Dockerfile.
[1]: https://fly.io/docs/languages-and-frameworks/node/#launch-th...
Well it still creates a fly.toml for you, which is still a new config file that I have to maintain across projects.
You update the toml file once (e.g if you have a release step), and then don't touch it again. Its more powerful than Heroku, so with that it gives you the option of adding additional config options.
I mean it even creates the basic file for you, I'm not sure what the issue is?