cespare / reflex

Run a command when files change

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Binary downloads

calebmer opened this issue · comments

One of this repository's proposed benefits as written in the readme: "Reflex has no dependencies. No need to install Ruby or anything like that." Yet the instillation reads:

$ go get github.com/cespare/reflex

I don't want to install go to use this library. Could this dependency be removed with binary downloads?

The README also says

TODO: provide compiled downloads for linux/darwin amd64.

But I've never gotten around to it, mostly because I have no need for this. Do you have a suggested method? I've considered using Bintray.

GitHub releases are preferable as that's where I generally check first.

Ah, I forgot that GH releases can included binaries. Good idea.

commented

@calebmer just uploaded some to my fork. compiled them with gox.
https://github.com/cescoferraro/reflex/releases/tag/v0.1.0

@cespare go get its not cacheble inside a Dockerfile there is a actual need for them on this repo

I would consider using https://github.com/goreleaser/goreleaser

It's quite awesome and integrates nicely into the CI workflow.

Here's a sample goreleaser config that would work well for this repo:

build:
  main: .
  binary: reflex
  goos:
    - darwin
    - linux
archive:
  replacements:
    amd64: 64-bit
    386: 32-bit
    darwin: MacOS
    linux: Linux
  files:
    - README.md
    - LICENSE

You can install goreleaser on your system with brew install goreleaser/tap/goreleaser or a manual download from https://github.com/goreleaser/goreleaser/releases.

Once you do that, you can run the following workflow:

export GITHUB_TOKEN=`YOUR_TOKEN` # Get this at https://github.com/settings/tokens
git tag -a v1.2.3 -m "your release message"
git push origin --tags
goreleaser

There is also Travis Integration.


This would be very much appreciated by many users who don't have the full go toolkit installed. I'm sure @sagikazarmark would be happy to answer any questions, as am I.

I've opened a PR #80 that should totally address the concerns of this issue.

OK, releases have binaries attached to them now.