It would be awesome if openwebui could use the Cloudron Tika server.

@nebulon understood; it's just in my testing environment (home) I'm use to connect my container via container_name:port without exposing the port. such as OpenWebUI connect to my Searxng because --- services: open-webui: searxng: container_name: searxng Now I understand this is not viable into a multi-domains, multi-services environment Do you think something similar is possible and viable ?

Perfect, thank you!

@ekevu123 said in Transcribe YouTube videos: this videos has captions, right? yes @ekevu123 said in Transcribe YouTube videos: Does it work for you? It doesn't work for me I don't currently have an instance running so can't check, sorry

@nebulon thanks for the tips and do you mind looking at this one ? https://forum.cloudron.io/topic/13320/accessing-the-openwebui-api/5?_=1740050615827 I'm unable to use the APP ID to connect to it.

@timconsidine no, but you can get GPU servers with AI niceties from Koyeb. I think They have a Ollama installer.

@girish Any chance of adding popular python packages to this Cloudron App? Quite a few functions here needing them: https://openwebui.com/functions Eg: https://openwebui.com/f/fovendor/flux_inpainting https://openwebui.com/f/fovendor/flux_gen

This would certainly be a very valuable addition to Cloudron. I have upvoted. That said, I guess that the configuration process could be challenging since there doesn't appear to be any point-and-click UI for that.

I forgot an important advantage: You're supporting open source.

I have found some answers about the Channels feature on Github: Channels Discussion Q: "I've been trying the new Channels feature. I can create Channels, assign groups and use it like a chat between group members. For the life of me, I have not found how to send a message to the AI model." A: "Has to be externally hosted with https://github.com/open-webui/bot for now, but built-in integration will be added soon." Integrating AI bots to Channels This repository provides an experimental boilerplate for building bots compatible with the Open WebUI "Channels" feature (introduced in version 0.5.0). It serves as a proof of concept to demonstrate bot-building capabilities while highlighting the potential of asynchronous communication enabled by Channels. Key Highlights Highly Experimental: This is an early-stage project showcasing basic bot-building functionality. Expect major API changes in the future. Extensible Framework: Designed as a foundation for further development, with plans to enhance APIs, developer tooling, and usability. Asynchronous Communication: Leverages Open WebUI Channels for event-driven workflows. ️ Getting Started with Examples This repository includes an /examples folder containing runnable example bots that demonstrate basic functionality. To run an example, execute the corresponding module using the -m flag in Python. For example, to run the ai example: python -m examples.ai Note: Ensure that your current working directory (PWD) is the root of this repository when running examples, as this is required for proper execution. Replace ai in the command above with the specific example you’d like to execute from the /examples folder. Disclaimer This project is an early-stage proof of concept. APIs will break and existing functionality may change as Open WebUI evolves to include native bot support. This repository is not production-ready and primarily serves experimental and exploratory purposes. Future Vision We aim to introduce improved APIs, enhanced developer tooling, and seamless native support for bots directly within Open WebUI. The ultimate goal is to make building bots easier, faster, and more intuitive.

BTW it seems to automatically recognize any audio file you throw at it. Either via Microphone or file upload and process TTS locally before passing it on to the selected model. Logs and graphs are pretty clear about this. Documentation however is not lol.

Are you referring to the Cloudron package? It is disabled by default in the Cloudron package in both Cloudron auth and non-Cloudron auth mode.

thanks for the info ...have awesome wonderful job

I think I can clarify this. Let's summarise what we all should know: Open Web UI needs to create a user automatically as admin. Even if you use Cloudron for authentication, this user will only have user rights. You need to log in using the account with the demo credentials and give your Cloudron account admin rights. There is no way around this account. If you decide to use the automatically created account, you cannot change its e-mail address, at least not using the GUI. It probably could be done in the database. If you want to delete this automatically created admin user, you don't need external software. Within the cloudron app settings, you can go into the terminal and connect to postgres, then there is a user table. This is probably the best approach.

thanks, fixed.

Yes, it's the same as branding - https://docs.cloudron.io/branding/#cloudron-name and https://docs.cloudron.io/user-directory/#openid-connect mention it.

@Lanhild is the pipeline can be installed with existing Openwebui in Cloudron? i don't see that kind of information in your Github

@Lanhild said in ETA for GPU support? Could we contribute to help it along?: A lot of companies that might deploy Cloudron for its ease of life features don't necessarily have a VPS with a GPU. Also, (might help you to deepen your Cloudron knowledge) Cloudron packages usually are only one component/application. Moreover, OpenWebUI is "just" a UI that supports connections to Ollama and isn't affiliated with it. Meaning that Ollama isn't a dependency of it at all. Excellent points @Lanhild - you've convinced me. And there are benefits on the Ollama side too. I would appreciate the benefit in using Cloudron to keep our Ollama installation automatically up to date on its own, for instance. In fact, given our remaining inability to modify the existing Cloudron OpenWebUI app to run with our GPUs, for our small clients we are now thinking this way - I.e. using Cloudron just for the OpenWebUI component and letting them connect to our separately hosted Ollama. It's a bit less convenient than we were hoping, but at least we'll still have segregated data and user management for each client in OpenWebUI. So now, I also want a Cloudron OpenWebUI app that does not come with bundled Ollama, so that I can be sure these customers don't hammer our CPUs and get frustrated by a slow user experiences.