Building Boundary from source requires:
- Go. Boundary developers keep current with new releases of Go in order to take advantage of new features and to ensure that security issues within Go are addressed. If building Boundary yourself, always use the latest version and keep current.
- Docker installed
- Basic development environment (git, xcode if you're on Mac, etc)
$ git clone https://github.com/hashicorp/boundaryor if you're using SSH auth for github,
$ git clone email@example.com:hashicorp/boundary
$ cd boundary
$ make install
The first time you run
make install it will build UI assets, which will take a
long time. After the initial build, you can update those assets to the
currently-pinned version via
Once you've built Boundary, the binary will be available at
<repo path>/bin/boundary. Move this
binary to somewhere in your
$PATH such as
If you need to cross compile boundary for another OS or architecture, use the GOOS and GOARCH
environment variable to set this. Example:
$ GOOS=linux GOARCH=amd64 make install
For more details, please consult the Boundary project on GitHub.
UI assets are built inside a Docker container. If this build step fails, try increasing memory and swap available to Docker.