Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ChatRTX 4.0 - Sharing Capabilities? #85

Open
ttrandynamic opened this issue Aug 6, 2024 · 3 comments
Open

ChatRTX 4.0 - Sharing Capabilities? #85

ttrandynamic opened this issue Aug 6, 2024 · 3 comments

Comments

@ttrandynamic
Copy link

I made minor changes to my ChatRTX 3.0 for sharing and after installing the new 4.0. With new interface, everything changes. There doesnt seem to be any ability to share app any longer.

@anujj
Copy link
Collaborator

anujj commented Aug 6, 2024

Yes, unlike gradio there is no sharing capability in the new version

@ttrandynamic
Copy link
Author

is there a development plan of achieving the sharing capability similar to gradio? I'm going to be honest, I really like the way ChatRTX functions and pitched this to my company and managed to route my home pc running chatrtx to a small group of employees within my company. We're going through the testing phase and finding solid project management case use (having chatrtx processes our construction contract specs for multiple projects, company standard docs etc). This new update removing the sharing capability, essentially kills the idea of implementing ChatRTX altogether.

@Alauz
Copy link

Alauz commented Oct 19, 2024

I was also deploying 3.0 with sharing to my colleagues previously and we're on the cusp of implementing it as an internal Chatbot with our existing knowledge base to make employee collaboration easier, however 4.0 just wiped out the entire project. Will there be a share button for further development? It's a real pity because this project had massive potential and going back to 3.0 really limits it. Also, the removal of using website links as part of the RAG completely decimates the project as well as our internal knowledgebase is stored on an intranet site. If we could further develop that to allow for web-based login as well it would make a shift to a login-required knowledge base possible if we were to extend it project wise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants