Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Added instructions for UI only image. #118

Merged
merged 3 commits into from
Apr 30, 2020
Merged

Added instructions for UI only image. #118

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c78089d
Added instructions for using existing UI only image.
joerg84 Apr 30, 2020
5a3a87c
Minor Improvements.
joerg84 Apr 30, 2020
b8c3a12
Typo fix and updated build instructions
cw00dw0rd Apr 30, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ Instead of each component storing its own metadata, a common Metadata Layer allo
## Use Cases
ArangoML Pipeline benefits many different scenarios including:
* Capture of Lineage Information (e.g., Which dataset influences which Model?)
* Capture of Audit Information (e.g, A given model was training two month ago with the following training/validation performance)
* Capture of Audit Information (e.g, A given model was training two months ago with the following training/validation performance)
* Reproducible Model Training
* Model Serving Policy (e.g., Which model should be deployed in production based on training statistics)
* Extension of existing ML pipelines through simple python/HTTP API
Expand Down
9 changes: 7 additions & 2 deletions documentation/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ If you would prefer an independent installation, docker containers for *torch* a

- [Torch](#torch)
- [Tensorflow](#tensorflow)

- [Frontend-only Docker image for the WebUI](#frontend-only-webui)

### Torch

Expand Down Expand Up @@ -76,7 +76,7 @@ The details are shown in the figure below.

5. Point your browser to [http://localhost:6529](http://localhost:6529) to get to the **ArangoDB** web user interface. The `root` password is `open sesame`.

### Tensorflow
### TensorFlow

1. Start the container:

Expand All @@ -96,6 +96,11 @@ The details are shown in the figure below.

5. Point your browser to: `http://localhost:6529` to get to the **ArangoDB** web user interface. The `root` password is `open sesame`.

### Frontend Only WebUI

To connect the UI against an existing Arangopipe instance, first update `REACT_APP_API_ROOT_URL` in the following command to be your desired ArangoDB endpoint:

`docker run -p 3000:3000 -e REACT_APP_API_ROOT_URL=http://localhost:8529/_db/arangopipe/ arangoml/arangopipe_ui:latest`


## Arangopipe Graph Model
Expand Down
8 changes: 5 additions & 3 deletions documentation/build/maintainers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,12 +88,14 @@ In order to sign-in to the ArangoML WebUI, a running ArangoDB instance is requir

1. Navigate to `arangopipe/arangopipe_frontend/app`

2. Run `docker-compose build`
2. Run `npm install`

3. Update `REACT_APP_API_ROOT_URL` in the following command to be your desired ArangoDB endpoint:
3. Run `docker-compose build`

4. Update `REACT_APP_API_ROOT_URL` in the following command to be your desired ArangoDB endpoint:
`docker run -p 3000:3000 -e REACT_APP_API_ROOT_URL=http://localhost:8529/_db/arangopipe/ arangopipe_frontend_app`

4. To confirm successful configuration, attempt to login at http://localhost:3000
5. To confirm successful configuration, attempt to login at http://localhost:3000