4 ms·
With `local repository` I meant not involving a thirdparty like Github or Gitlab which is a requirement for some Heroku-like providers. `git push heroku` is ver
by 5fnheluzdj 4y ago
With `local repository` I meant not involving a thirdparty like Github or Gitlab which is a requirement for some Heroku-like providers. `git push heroku` is very nice to have - for me it would be enough to not having to leave the terminal as it seems to be the case.
Last time I tried fly.io I had to provide payment information before doing something useful. I'll give it another try as you suggested.
- bradgessler 4y agoGot it! There's no plans to implement git repos in the same way Heroku is doing it (FWIW I love how Heroku does this). When Heroku introduced this feature, cloud CI services were practically non-existent. Today a similar effect can be achieved in Github, Gitlab, etc. with their CI integrations (See https://fly.io/docs/app-guides/continuous-deployment-with-github-actions/ https://fly.io/docs/app-guides/continuous-deployment-with-gi... for Github) I realize that's what you're trying to avoid. In your case I'd recommend running `fly deploy` from your CLI If you don't want to leave the CLI. You could wire this up as a git hook either on your workstation or third-party git server. I recognize this isn't the same thing as Heroku, so I'm calling these work arounds :-)