Open jfowl opened 1 year ago
You'd always be installing something on each run unless flyio/flyctl also comes with build tools for rust, node, go, etc, and users would be very likely to want to replace the runner image with their own.
I can share a preview deploy script I have for GitHub Actions if you end up building this, it may be a good starting point for the GitLab one.
(I just realized this is a 2 year necro (sorry?))
I would offer to write that, I would just like Fly's blessing before wasting time on submitting the PR.
As a basis, this blog post could be used: https://fly.io/blog/continuous-deployment-with-gitlab/
Although I would probably use https://hub.docker.com/r/flyio/flyctl instead of manually installing it on each job run. In addition: Merge-Request preview deployments.