Hashiconf docs changes (#2178)

Co-authored-by: Robin Beck <stellarsquall@users.noreply.github.com> Co-authored-by: XingLu Wang <95828202+xingluw@users.noreply.github.com> Co-authored-by: Loann Le <84412881+taoism4504@users.noreply.github.com> Co-authored-by: Jeff Mitchell <jeffrey.mitchell@gmail.com> Co-authored-by: irenarindos <irena.rindos@gmail.com> Co-authored-by: Irena Rindos <irenarindos@users.noreply.github.com> Co-authored-by: Louis Ruch <louisruch@gmail.com> Co-authored-by: XingLu Wang <xinglu.wang@hashicorp.com> Co-authored-by: XingLu Wang <95828202+xingluw@users.noreply.github.com>
2022-06-22 02:37:49 -04:00
1 parent 5c83182cc7
commit c05fa66096
@@ -1,38 +0,0 @@
---
-layout: docs
-page_title: Documentation
-description: Building Boundary
---
-
-# Building Boundary
-
-Building Boundary from source requires:
-
- [Go](https://golang.org/dl/) 1.14 or greater. (Note that HashiCorp currently develops against Go 1.15.)
- `make` installed
- [Docker](https://docs.docker.com/get-docker/) installed
- Basic development environment (git, xcode if you're on Mac, etc)
-
-1. `$ git clone https://github.com/hashicorp/boundary` or if you're using SSH auth for
-   github, `$ git clone git@github.com:hashicorp/boundary`
-2. `$ cd boundary`
-3. `$ 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 `make build-ui`.
-
-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 `/usr/local/bin`.
-
-## Cross Platform Build
-
-If you need to cross compile boundary for another OS or architecture, use the [GOOS and GOARCH](https://github.com/hashicorp/boundary/blob/master/scripts/build.sh#L26)
-environment variable to set this. Example: `$ GOOS=linux GOARCH=amd64 make install`
-
-For more details, please consult the [Boundary project on GitHub](https://github.com/hashicorp/boundary#build-and-start-boundary-in-dev-mode).
-
-## Troubleshooting
-
-UI assets are built inside a Docker container. If this build step fails, try
-increasing memory and swap available to Docker.
@@ -1,10 +0,0 @@
---
-layout: docs
-page_title: Developing Boundary
-description: Developing Boundary
---
-
-# Developing Boundary
-
-The side-bar contains some common development tasks, but for the most up-to-date information about developing Boundary, please consult
-our [project on GitHub](https://github.com/hashicorp/boundary) for more information.
@@ -1,21 +0,0 @@
---
-layout: docs
-page_title: Developing the UI
-description: Developing the Boundary User Interface
---
-
-# Developing the Boundary User Interface
-
-For detailed instructions and the most up-to-date information on developing the
-Boundary admin UI, please consult [the project README on GitHub](https://github.com/hashicorp/boundary-ui).
-
-## Run a Local Fork of the UI Locally in Dev Mode
-
-If you're developing the Boundary UI locally you can point a dev mode server at a
-local checkout of the repo without building it into the binary. We call this
-directory a passthrough directory, and you can enable it using an env var while in
-conjunction with running Boundary in dev mode:
-
-```bash
-BOUNDARY_DEV_UI_PASSTHROUGH_DIR=../boundary-ui/ui/admin/dist boundary dev
-```