github.com/szyn/goreleaser@v0.76.1-0.20180517112710-333da09a1297/www/content/introduction.md (about)

     1  ---
     2  title: Introduction
     3  weight: 1
     4  menu: true
     5  ---
     6  
     7  [GoReleaser](https://github.com/goreleaser/goreleaser) is a release automation
     8  tool for Go projects, the goal is to simplify the build, release and
     9  publish steps while providing variant customization options for all steps.
    10  
    11  GoReleaser is built for CI tools; you only need to
    12  [download and execute it](#ci_integration) in your build script.
    13  You can [customize](#customization) your release process by
    14  creating a `.goreleaser.yml` file.
    15  
    16  The idea started with a
    17  [simple shell script](https://github.com/goreleaser/old-go-releaser),
    18  but it quickly became more complex and I also wanted to publish binaries via
    19  Homebrew taps, which would have made the script even more hacky, so I let go of
    20  that and rewrote the whole thing in Go.
    21  
    22  ## Installing Goreleaser
    23  
    24  There are three ways to get going install GoReleaser:
    25  
    26  ### Using homebrew
    27  
    28  ```sh
    29  brew install goreleaser/tap/goreleaser
    30  ```
    31  
    32  ### Using Scoop
    33  
    34  ```sh
    35  scoop bucket add goreleaser https://github.com/goreleaser/scoop-bucket.git
    36  scoop install goreleaser
    37  ```
    38  
    39  > Check the [tap source](https://github.com/goreleaser/homebrew-tap) for
    40  > more details.
    41  
    42  ## Manually
    43  
    44  Download your preferred flavor from the [releases page](https://github.com/goreleaser/goreleaser/releases/latest) and install
    45  manually.
    46  
    47  ### Using go get
    48  
    49  Note: this method requires Go 1.10+.
    50  
    51  ```console
    52  $ go get -d github.com/goreleaser/goreleaser
    53  $ cd $GOPATH/src/github.com/goreleaser/goreleaser
    54  $ dep ensure -vendor-only
    55  $ make build
    56  ```
    57  
    58  It is recommended to also run `dep ensure` to make sure that the dependencies
    59  are in the correct versions.