Skip to content

Commit

Permalink
Use gox for building, update instructions for releasing and consuming
Browse files Browse the repository at this point in the history
binaries.
  • Loading branch information
f2prateek committed Jul 15, 2016
1 parent f3305af commit 4f9dea9
Show file tree
Hide file tree
Showing 3 changed files with 9 additions and 12 deletions.
2 changes: 1 addition & 1 deletion Makefile
@@ -1,5 +1,5 @@
build:
go build -o bin/segment-proxy
gox -output="bin/{{.Dir}}_{{.OS}}_{{.Arch}}"

server:
go run main.go
Expand Down
4 changes: 1 addition & 3 deletions README.md
Expand Up @@ -26,9 +26,7 @@ Usage of proxy:

### Via prebuilt binaries.

1. Run `wget https://github.com/segmentio/segment-proxy/releases/download/1.0.0/proxy`.
2. Run `chmod +x proxy`.
3. Run `./proxy`.
Download the latest binaries from [Github](https://github.com/segmentio/segment-proxy/releases).

### Via Docker

Expand Down
15 changes: 7 additions & 8 deletions RELEASING.md
@@ -1,11 +1,10 @@
# Releasing

1. Verify the build by running `make build test docker`.
2. Update the version in `README.md`.
3. Update the `CHANGELOG.md` for the impending release.
4. Run `git commit -am "Prepare for release X.Y.Z."` (where X.Y.Z is the new version).
5. Run `git tag -a X.Y.Z -m "Version X.Y.Z"` (where X.Y.Z is the new version).
6. Run `git push && git push --tags`.
7. Run `make docker-push`.
8. Run `github-release release --user segmentio --repo segment-proxy --tag X.Y.Z --name "X.Y.Z"`
8. Run `github-release upload --user segmentio --repo segment-proxy --tag X.Y.Z --name "X.Y.Z" --file bin/segment-proxy`.
2. Update the `CHANGELOG.md` for the impending release.
3. Run `git commit -am "Prepare for release X.Y.Z."` (where X.Y.Z is the new version).
4. Run `git tag -a X.Y.Z -m "Version X.Y.Z"` (where X.Y.Z is the new version).
5. Run `git push && git push --tags`.
6. Run `make docker-push`.
7. Create a release on [Github](https://github.com/segmentio/segment-proxy/releases).
8. Upload the files from the `bin` folder.

0 comments on commit 4f9dea9

Please sign in to comment.