Skip to content

Conversation

@dominikkawka
Copy link
Member

Still have to write a section on skills/ knowledge contributions and being able to view them, would like some feedback on what I've currently written also.

@vishnoianil
Copy link
Member

cc : @instructlab/ui-maintainers

Copy link
Member

@vishnoianil vishnoianil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the awesome work @dominikkawka . Review and provides minor review comments.


Set the `Homepage URL` and the `Authorization Callback URL` to `http://localhost:3000`.

Update the .env files with the new ID and secret ID generated, `OAUTH_GITHUB_ID` = Client ID, `OAUTH_GITHUB_SECRET` = Client Secret No newline at end of file
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Creation of the OAuth App will create the client_id, that is set to OAUTH_GITHUB_ID, but it doesn't automatically create the secret. Once the app is created, on the main page it provides an option to create a secret. Press the Create Secret button and it will generate a secret for you. Copy the secret and set it to OAUTH_GITHUB_SECRET value.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If user don't want to setup the OAuth in his own org, we would recommend users to reach out to UI maintainers over the #ui slack channel and they will be happy to share the details of the dev OAuth app setup for the instructlab-public org for test-taxonomy.


![UI No Model Response](../images/user-interface/ui_no_model_response.png)

However, the model won't reply because a granite/ merlinite model endpoint hasn't been given. Instead, we will create a new custom model endpoint, using our locally hosted quantised model from step 1.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@dominikkawka Focus of this document is dev environment or the direct users of ui.instructlab.ai? Details looks good for dev setup, but using the ui.instructlab.ai they can chat with both merlinite and granite models.


You will have 3 fields to fill out

* The URL, where your customised model is hosted, which would be `http://127.0.0.1:8000/`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assuming that the customized model is running where the UI is running. If it's running on different machine, it needs to be the reachable ip address of that machine. Port number should be the one where customize model serve is listening on.


* The Model Name, `merlinite-7b-lab-Q4_K_M.gguf`

* API Key, you may put any text in here, in this case I've put in `randomCharacters`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or if user is setting up an API key, they should provide the key here.


### Taxonomy Directory Path

Specify where in the taxonomy this skill would belong in. As the taxonomy fills, it will become more complex, make sure to give a concise location to keep the taxonomy organised.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Specify where in the taxonomy this skill would belong in. As the taxonomy fills, it will become more complex, make sure to give a concise location to keep the taxonomy organised.
Specify where in the taxonomy repository directory structure this skill would belong in. As the taxonomy fills in with more skills, it will become more complex, make sure to give a concise location to keep the taxonomy organised.

![Forked Repository Showcase](../images//user-interface/ui_knowledge_repo_created.png)

If you've already uploaded the markdown file to your github, you can switch to manually adding the document, and entering the `commit sha`.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be helpful if we add the snapshot of the Manually adding the doc details page.


The InstructLab User Interface (UI) is an additional component in the InstructLab project to make Knowledge/Skills
contributions more accessible to the general user. Instead of having to edit a `qna.yaml` file,
users can fill out the contribution forms on the web. The user can also view their all of their contributions in a
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
users can fill out the contribution forms on the web. The user can also view their all of their contributions in a
users can fill out the contribution forms on the web. The user can also view all of their contributions in a

!!! note
To log into the UI and submit Knowledge and Skills contributions, you must be a member of the [instructlab-public](https://github.com/instructlab-public) github repository.

If you aren't a member of the repository, but still wish to experiment with the UI, we recommend you to download it locally.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should recommend users to reach out to UI maintainers to add them to the instructlab-public org. If they don't want to join but still want to experiment, they can set it up locally.


* Have a [github](https://github.com/) account

* Have InstructLab installed
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not a mandatory requirement. This is needed only if user wants to host the endpoint locally on the same machine.


When the install is finished, start the UI by running:

`make start-dev-local`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should mention how to stop the ui as well. User can use command make stop-dev-local to stop the dev environment.

@dominikkawka dominikkawka force-pushed the ui branch 3 times, most recently from ce4f68b to ea334c4 Compare October 16, 2024 12:00
Signed-off-by: DominikKawka <dkawka@redhat.com>
Signed-off-by: DominikKawka <dkawka@redhat.com>
Signed-off-by: DominikKawka <dkawka@redhat.com>
Signed-off-by: DominikKawka <dkawka@redhat.com>
Signed-off-by: DominikKawka <dkawka@redhat.com>
Signed-off-by: DominikKawka <dkawka@redhat.com>
@jjasghar
Copy link
Member

I just did a flip through, this is amazing work Dom, great job.

@kelbrown20
Copy link
Contributor

kelbrown20 commented Nov 11, 2024

Im not an expert on the UI, but on the docs side this looks awesome to me! Great work! I think we should get this merged soon whenever its ready! 🍾

@jjasghar jjasghar merged commit 6174543 into instructlab:main Nov 11, 2024
1 check passed
@vishnoianil
Copy link
Member

I dropped the ball on reviewing it again, but the content looks great!. Thanks for pulling this together @dominikkawka . I pushed a PR to UI repo as well, that points to this brand new documentation. Awesome work, you rock !!

@dominikkawka dominikkawka deleted the ui branch April 14, 2025 12:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants