@firmansi https://docs.cloudron.io/packaging/tutorial/

thanks, fixed.

So I logged out and saw that I could use the CLoudron login:
image.png

I logged in with that and now there are two users, and my cloudron user IS one of the admin.
image.png

I guess this is one way to make sure the email is a specific one, but I don't know if you want your Cloudron user to be an admin by default.

I still can't determine why you have TWO users, one of which was automatically made. Try installing again, and keep track of your steps so help troubleshoot this if it repeats. Good luck.

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. 🙂

I resolved the issue. I had the directory set to /media/TSYSAI instead of just /media.

Thanks!

@micmc yes, hopefully anythingllm can also come to live in Cloudron

ok
I think it was RAM issue
when there is no enough RAM. it gives this error.

thanks guys

@micmc agreed i do use it on my computer but i was wanting to let my buddies play with it but hey thanks

This is out now

@chetbaker App is totally unusable and unuseful at this point... Especially for those like me don't have right skills and knowledge to move forward...

thanks I was able to reproduce and fix it. It will be part of the next package update

Awesome, now everything works just fine...salute for cloudron team

We would have to adjust the package to pre-configure the app to use optionally redis. However this is only relevant for multi-instance setups which is anyways not the case for Cloudron and only relevant for instances with many concurrent users, which is likely not the main focus for this app on Cloudron. So so far this optional redis is out of scope.

From the Changelog: Enhanced load balancing capabilities for multiple instance setups

The Open Web UI project initially started out as a Ollama frontend. To run local models, one needs GPU support and Cloudron currently does not have GPU support. Over time, Open Web UI has shifed to be a frontend for OpenAI API compatible services . It is also now possible to configure Ollama in another computer which has a GPU and then point Open Web UI to use that Ollama.

I guess we can mark this as stable since it's still useful while we figure out GPU support in Cloudron.