[GH-ISSUE #7] GitHub Releases for Build version of this chat app? #50564

Closed
opened 2026-05-05 10:34:11 -05:00 by GiteaMirror · 3 comments
Owner

Originally created by @coolaj86 on GitHub (Oct 21, 2023).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/7

Originally assigned to: @tjbck on GitHub.

I'm looking to create an installer for ollama for Webi (https://webinstall.dev), and some sort of UI like this (to make it more immediately accessible to people installing it).

Would you please release the pre-built version via GitHub Releases so that it can be used with just ollama and caddy without all of node?

Automating Releases

I could help you get it so that basically when you git tag v1.1.1 && git push --tags a .github/workflows automatically builds and uploads it to the Releases section using gh

Originally created by @coolaj86 on GitHub (Oct 21, 2023). Original GitHub issue: https://github.com/open-webui/open-webui/issues/7 Originally assigned to: @tjbck on GitHub. I'm looking to create an installer for ollama for Webi (https://webinstall.dev), and some sort of UI like this (to make it more immediately accessible to people installing it). Would you please release the pre-built version via GitHub Releases so that it can be used with just `ollama` and `caddy` without all of node? ## Automating Releases I could help you get it so that basically when you `git tag v1.1.1 && git push --tags` a `.github/workflows` automatically builds and uploads it to the Releases section using [`gh`](https://webinstall.dev/gh/)
Author
Owner

@tjbck commented on GitHub (Oct 22, 2023):

Sounds good. After the #10 merge, could you add the files required to automate the process and create a separate pull request? Thanks a lot.

<!-- gh-comment-id:1773960997 --> @tjbck commented on GitHub (Oct 22, 2023): Sounds good. After the #10 merge, could you add the files required to automate the process and create a separate pull request? Thanks a lot.
Author
Owner

@coolaj86 commented on GitHub (Oct 22, 2023):

I probably won't have time to do that this week, but I'll make some notes now and get around to it when I can.

Overview + Docs

Here's how to publish locally with gh

There's already an action in the repo that goes through the build process:

This is what would be modified to create a workflow that operates on tags rather than branches:

on:  
  push:
    tags:
      - '*'

All actions come with a github.token that can be assigned to scripts via ENVs:

jobs:
    Build-GitHub-Pages:
        runs-on: ubuntu-20.04
        env:
          GH_BASIC_AUTH: "x-access-token:${{ github.token }}"
          GH_TOKEN: "${{ github.token }}"

I think what would be needed, however, is a token specifically created to be a New Repository Secret:

It would need a token with specific permissions for Releases, which would be either of these:

  • repo (full repo access)
  • Contents (read+write fine-grained control)
    Repository contents, commits, branches, downloads, releases, and merges.

Much of my personal notes are at:

<!-- gh-comment-id:1774033262 --> @coolaj86 commented on GitHub (Oct 22, 2023): I probably won't have time to do that this week, but I'll make some notes now and get around to it when I can. ## Overview + Docs Here's how to publish locally with `gh` - https://github.com/jmorganca/ollama/blob/main/scripts/publish.sh There's already an action in the repo that goes through the build process: - https://github.com/ollama-webui/ollama-webui/blob/main/.github/workflows/node.js.yaml#L3 This is what would be modified to create a workflow that operates on tags rather than branches: ```yaml on: push: tags: - '*' ``` All actions come with a `github.token` that can be assigned to scripts via ENVs: ```yaml jobs: Build-GitHub-Pages: runs-on: ubuntu-20.04 env: GH_BASIC_AUTH: "x-access-token:${{ github.token }}" GH_TOKEN: "${{ github.token }}" ``` I think what would be needed, however, is a token specifically created to be a **New Repository Secret**: - <https://github.com/settings/tokens> - <https://github.com/ollama-webui/ollama-webui/settings/secrets/actions> It would need a token with specific permissions for Releases, which would be either of these: - `repo` (full repo access) - > _Contents_ (read+write fine-grained control) > Repository contents, commits, branches, downloads, releases, and merges. Much of my personal notes are at: - <https://github.com/coolaj86/explore-github-actions/>
Author
Owner

@tjbck commented on GitHub (Dec 24, 2023):

Again, this would also be ideal for https://github.com/ollama-webui/ollama-webui-lite now (stripped down version of ollama-webui without the backend part), I'll think of ways to include this in the other repo. Thanks!

<!-- gh-comment-id:1868471213 --> @tjbck commented on GitHub (Dec 24, 2023): Again, this would also be ideal for https://github.com/ollama-webui/ollama-webui-lite now (stripped down version of ollama-webui without the backend part), I'll think of ways to include this in the other repo. Thanks!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#50564