Add mechanism for bundling UI assets. (#153)
* Add mechanism for bundling UI assets. The scripts/uigen.sh script will check out the UI repo, build assets, create a static assets file, and clean up. The dev Makefile target has been modified to run this script if no assets file is found. There is also a build-ui target that will unilaterally update (the dev target only builds if the file isn't found, but doesn't update). The handler has been updated to add the default org ID as a header if the request path is "/". Co-authored-by: Randall Morey <randall@randallmorey.com>
This commit is contained in:
1 parent
8d8bb42418
commit
8da4effd5e
10 files changed
+147
-65
No files matched your search
@@ -89,6 +89,15 @@ This will build Watchtower. Once complete, run Watchtower in `dev` mode:
|
||||
|
||||
```./$GOPATH/bin/watchtower dev```
|
||||
|
||||
#### Specify a UI Commitish at Build Time
|
||||
|
||||
The default UI build branch is `develop` from [the UI
|
||||
repo](https://github.com/hashicorp/watchtower-ui). A different commitish from
|
||||
which to build UI assets may be specified via the UI_COMMITISH environment
|
||||
variable. For example:
|
||||
|
||||
```UI_COMMITISH=feature-branch make dev```
|
||||
|
||||
### Download and Run from Release Page
|
||||
|
||||
Download the latest release of the server binary and appropriate desktop
|
||||
@@ -96,17 +105,17 @@ client(s) from our [releases page]
|
||||
|
||||
### Start Watchtower
|
||||
|
||||
Start the server binary with:
|
||||
Start the server binary with:
|
||||
|
||||
```watchtower dev```
|
||||
|
||||
This will start a Controller service listening on `http://127.0.0.1:9200` for
|
||||
incoming API requests and a Worker service listening on the same address/port for
|
||||
incoming session requests. It will also create various default Catalogs and Sets,
|
||||
and display various bits of information, such as a username and password that can
|
||||
This will start a Controller service listening on `http://127.0.0.1:9200` for
|
||||
incoming API requests and a Worker service listening on the same address/port for
|
||||
incoming session requests. It will also create various default Catalogs and Sets,
|
||||
and display various bits of information, such as a username and password that can
|
||||
be used to log in.
|
||||
|
||||
### Configuring Resources
|
||||
### Configuring Resources
|
||||
|
||||
For a simple test of Watchtower in `dev` mode you don't generally need to
|
||||
configure any resources at all! But it's useful to understand what `dev` mode
|
||||
|
||||
Reference in new issue
Block a user