-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Releases / Binary Distribution #21
Comments
Yeah that sounds like a good idea. I'm not very across how to set up a good release workflow. There's a PR (#20) up that does this for ubuntu but it's pending my question about how to update etc. Does anybody have some pointers on the best way to do this? |
Maybe build binary on some kind of CI service like travis-ci and then upload it somewhere with link attached in README. |
@jesseduffield What I did for my projects is that on my buildbot I use AFAIK circle and travis both have a github releases API that also allows you to push the binaries to github afterwards, but I don't know their limitations on that. (My binaries were too big, as it was around 12GB of system images etc. so I had to use a VPS for that.) |
Hey, I started to use GoReleaser a few days ago for some of my Go projects. You have a pretty simple .goreleaser.yml in your repository and when you run Felix |
I've used Travis to build binaries before for releases on github, then you can just have download based instructions (or use those binaries in package managers): example PR on atombender/ktail with setup instructions. |
I ended up using travis ci and we've got releases / binaries working :) Please feel free to have a look at the .travis.yml and see if there's any improvements that could be made |
Can we also build binaries for other architectures like arm and arm64? |
yep, getting onto that now |
we have LIFTOFF https://github.com/jesseduffield/lazygit/releases (note I've removed the version number from the end of the file because we now store that in the binary itself) |
closing |
@jesseduffield What do you think about adding 32 bit builds to the bunch? |
@Tallefer I've chucked 32 bit builds in the latest release :) https://github.com/jesseduffield/lazygit/releases/tag/v0.1.66 |
Is there a way to distribute binaries in this project by using the releases/tags for it?
It would heavily improve the installation for people not familiar with go and people that don't have a working go setup and just want to build a simple package for a binary.
The text was updated successfully, but these errors were encountered: