[PR #15269] [CLOSED] Develop #62635

Closed
opened 2026-05-06 06:55:10 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/15269
Author: @JeanBaptisteBolh
Created: 6/24/2025
Status: Closed

Base: mainHead: develop


📝 Commits (8)

  • a4f24d2 add searxng config
  • a52c624 custom scripts update readme custom docker compose
  • 53506d9 Merge pull request #1 from Applied-General-Intelligence-Inc/searxng-conf
  • 47c1432 update dokcer compose to include openai api key
  • 216c38a add pipelines test
  • 5c7d6bc pieplines done
  • d17b632 Merge pull request #2 from Applied-General-Intelligence-Inc/pipelines
  • 655c32c docker shenanigans to make this shiz work

📊 Changes

9 files changed (+643 additions, -2 deletions)

View changed files

.github/workflows/deploy-dc.yml (+105 -0)
📝 Dockerfile (+1 -1)
📝 README.md (+219 -1)
docker-compose.custom.yml (+100 -0)
manage.sh (+136 -0)
ollama/Dockerfile (+14 -0)
searxng_settings.yml (+13 -0)
start.sh (+27 -0)
stop.sh (+28 -0)

📄 Description

Pull Request Checklist

Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.

Before submitting, make sure you've checked the following:

  • Target branch: Please verify that the pull request targets the dev branch.
  • Description: Provide a concise description of the changes made in this pull request.
  • Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
  • Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
  • Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
  • Testing: Have you written and run sufficient tests to validate the changes?
  • Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
  • Prefix: To clearly categorize this pull request, prefix the pull request title using one of the following:
    • BREAKING CHANGE: Significant changes that may affect compatibility
    • build: Changes that affect the build system or external dependencies
    • ci: Changes to our continuous integration processes or workflows
    • chore: Refactor, cleanup, or other non-functional code changes
    • docs: Documentation update or addition
    • feat: Introduces a new feature or enhancement to the codebase
    • fix: Bug fix or error correction
    • i18n: Internationalization or localization changes
    • perf: Performance improvement
    • refactor: Code restructuring for better maintainability, readability, or scalability
    • style: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
    • test: Adding missing tests or correcting existing tests
    • WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry

Description

  • [Concisely describe the changes made in this pull request, including any relevant motivation and impact (e.g., fixing a bug, adding a feature, or improving performance)]

Added

  • [List any new features, functionalities, or additions]

Changed

  • [List any changes, updates, refactorings, or optimizations]

Deprecated

  • [List any deprecated functionality or features that have been removed]

Removed

  • [List any removed features, files, or functionalities]

Fixed

  • [List any fixes, corrections, or bug fixes]

Security

  • [List any new or updated security-related changes, including vulnerability fixes]

Breaking Changes

  • BREAKING CHANGE: [List any breaking changes affecting compatibility or functionality]

Additional Information

  • [Insert any additional context, notes, or explanations for the changes]
    • [Reference any related issues, commits, or other relevant information]

Screenshots or Videos

  • [Attach any relevant screenshots or videos demonstrating the changes]

Contributor License Agreement

By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/15269 **Author:** [@JeanBaptisteBolh](https://github.com/JeanBaptisteBolh) **Created:** 6/24/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `develop` --- ### 📝 Commits (8) - [`a4f24d2`](https://github.com/open-webui/open-webui/commit/a4f24d208b58215c8b1687cfb4333bbc66112f68) add searxng config - [`a52c624`](https://github.com/open-webui/open-webui/commit/a52c624339ec59cc8c7f31b721fd31fdcd25d3ea) custom scripts update readme custom docker compose - [`53506d9`](https://github.com/open-webui/open-webui/commit/53506d9f502fcddf2de8d5024614d8f153cff3fe) Merge pull request #1 from Applied-General-Intelligence-Inc/searxng-conf - [`47c1432`](https://github.com/open-webui/open-webui/commit/47c1432951d80c6f40d9ba56d4dff5d514056637) update dokcer compose to include openai api key - [`216c38a`](https://github.com/open-webui/open-webui/commit/216c38a8c77196399e5fcf9424f9615f52d9758f) add pipelines test - [`5c7d6bc`](https://github.com/open-webui/open-webui/commit/5c7d6bc7cf50de3260e19ddf155447df8fd1cae2) pieplines done - [`d17b632`](https://github.com/open-webui/open-webui/commit/d17b632a0f705ead96d00ff16156933c95ca186a) Merge pull request #2 from Applied-General-Intelligence-Inc/pipelines - [`655c32c`](https://github.com/open-webui/open-webui/commit/655c32c67e693969f95c3b42ef693d65fe0aa503) docker shenanigans to make this shiz work ### 📊 Changes **9 files changed** (+643 additions, -2 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/deploy-dc.yml` (+105 -0) 📝 `Dockerfile` (+1 -1) 📝 `README.md` (+219 -1) ➕ `docker-compose.custom.yml` (+100 -0) ➕ `manage.sh` (+136 -0) ➕ `ollama/Dockerfile` (+14 -0) ➕ `searxng_settings.yml` (+13 -0) ➕ `start.sh` (+27 -0) ➕ `stop.sh` (+28 -0) </details> ### 📄 Description # Pull Request Checklist ### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) and describe your changes before submitting a pull request. **Before submitting, make sure you've checked the following:** - [ ] **Target branch:** Please verify that the pull request targets the `dev` branch. - [ ] **Description:** Provide a concise description of the changes made in this pull request. - [ ] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [ ] **Documentation:** Have you updated relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs), or other documentation sources? - [ ] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [ ] **Testing:** Have you written and run sufficient tests to validate the changes? - [ ] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards? - [ ] **Prefix:** To clearly categorize this pull request, prefix the pull request title using one of the following: - **BREAKING CHANGE**: Significant changes that may affect compatibility - **build**: Changes that affect the build system or external dependencies - **ci**: Changes to our continuous integration processes or workflows - **chore**: Refactor, cleanup, or other non-functional code changes - **docs**: Documentation update or addition - **feat**: Introduces a new feature or enhancement to the codebase - **fix**: Bug fix or error correction - **i18n**: Internationalization or localization changes - **perf**: Performance improvement - **refactor**: Code restructuring for better maintainability, readability, or scalability - **style**: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.) - **test**: Adding missing tests or correcting existing tests - **WIP**: Work in progress, a temporary label for incomplete or ongoing work # Changelog Entry ### Description - [Concisely describe the changes made in this pull request, including any relevant motivation and impact (e.g., fixing a bug, adding a feature, or improving performance)] ### Added - [List any new features, functionalities, or additions] ### Changed - [List any changes, updates, refactorings, or optimizations] ### Deprecated - [List any deprecated functionality or features that have been removed] ### Removed - [List any removed features, files, or functionalities] ### Fixed - [List any fixes, corrections, or bug fixes] ### Security - [List any new or updated security-related changes, including vulnerability fixes] ### Breaking Changes - **BREAKING CHANGE**: [List any breaking changes affecting compatibility or functionality] --- ### Additional Information - [Insert any additional context, notes, or explanations for the changes] - [Reference any related issues, commits, or other relevant information] ### Screenshots or Videos - [Attach any relevant screenshots or videos demonstrating the changes] ### Contributor License Agreement By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-05-06 06:55:10 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#62635