Who is version 2 for? #1329
Replies: 10 comments 14 replies
-
I just wanted to second this sentiment. I love and appreciate all the work that has been done, but getting version 2 running in any non development capacity in my own environment has been frustrating. Supabase is an absolute nightmare to deal with and adds too much complexity to self host. Really wish there was some easier deployment options to run this thing. More than willing to help out. |
Beta Was this translation helpful? Give feedback.
-
Each users has their own account and own chat sessions. I run it on a server for multiple users and no issues |
Beta Was this translation helpful? Give feedback.
-
Supabase defenitely makes life difficult for those of us with existing managed Postgres installations. The documentation for setting up Supabase with an existing Postgres instance is lacking to say the least, and is the biggest blocker to adoption in my case. Using the standard Supabase postgres image is not feasible as introducing new data stores with associated maintenance, uptime, and backup requirements is a non-starter. I'm wondering how much effort it would be to add an adapter layer that allows one to swap out different data stores. |
Beta Was this translation helpful? Give feedback.
-
Also having issues with the main branch. I opened an issue related to setup problems and it was closed very quickly without discussion #1399 I know the policy is that issues unrelated to the direct repo would be closed (i.e. getting it set up on certain cloud providers) which is totally reasonable. However, this seemed to be related. I am super thankful for all the work here, I just am a bit confused by the state of the project. It is ok to still use the legacy branch? |
Beta Was this translation helpful? Give feedback.
-
Who is version 2 for? The readme says "The open-source AI chat app for everyone." It might be more accurate to say it's for a rather small group of software developers who happen to have experience with a very specific tech stack, which is perhaps not nearly as ubiquitous as the young creator assumes. This is the open source world so I can't really complain, but this seems closer to a hobby project than practically usable software. The fact that I'm here shows that I see the potential, but the barriers to deployment seem way too high. I do appreciate the effort and I'll keep checking back to see how things develop. |
Beta Was this translation helpful? Give feedback.
-
@Jonneal3 I believe they are referring to Supabase, not the front-end stack. |
Beta Was this translation helpful? Give feedback.
-
I'm a bit of a novice, but seemed to deploy okay. |
Beta Was this translation helpful? Give feedback.
-
Just for anyone arriving at this thread recently... I wanted to give a shout out to @mckaywrigley who's updated the README.md. It says he's looking into simpler deployment - thank you! |
Beta Was this translation helpful? Give feedback.
-
I agree with all the above: I love chatbot-ui, I hate Supabase (with a passion). I wish we could have a simple, easily deployable docker build. I'm willing to help make it happen, even if it means a fork. |
Beta Was this translation helpful? Give feedback.
-
Hi curious what’s wrong with Supabase? |
Beta Was this translation helpful? Give feedback.
-
Version 1 had a simple docker image that I could take, and deploy for people internally to use. We could point it at an Azure OpenAI connection and everything just worked.
Looking at version 2, there's no docker image - just a series of complex(ish) steps to set up. And it's not even clear if it's safe for multiple people to use any more - if I go through all the steps to install all the things, will users have different chat sessions or will they all share one?
Is ChatBotUI mostly just a tool for people to run themselves now, rather than to install internally for multiple people to share?
Beta Was this translation helpful? Give feedback.
All reactions