Separate the Chat logic from the system logic #82

New Issue

2025-11-11T14:04:35-06:00

GiteaMirror commented

2025-11-11 14:04:35 -06:00

Originally created by @oliverbob on GitHub (Dec 13, 2023).

Is there a way to create or separate the chat logic from the system/administrative logic? Its good to be able to add a feature that allows server owners to disable/enable features or settings or administrator privileges (at build or at runtime), such as:

Chat Only
Disable Model View (disable dropdown selection of models)
Have a default model
Hide download
Enable default model
Disable Settings View (or at least, show only parts of system settings). This is beneficial to protect accidental deletion of models.
Enable search view (in stead of chat interface, bring the text area to the center of the screen (just like google search).

If contributors are busy, I'd like to be able to know the actual files that deals with this view, so I can play around with it.

Overall, I'm happy with the result of the latest release. Kudos to the contributors.

Thanks.

Originally created by @oliverbob on GitHub (Dec 13, 2023). Is there a way to create or separate the chat logic from the system/administrative logic? Its good to be able to add a feature that allows server owners to disable/enable features or settings or administrator privileges (at build or at runtime), such as: - Chat Only - Disable Model View (disable dropdown selection of models) - Have a default model - Hide download - Enable default model - Disable Settings View (or at least, show only parts of system settings). This is beneficial to protect accidental deletion of models. - Enable search view (in stead of chat interface, bring the text area to the center of the screen (just like google search). If contributors are busy, I'd like to be able to know the actual files that deals with this view, so I can play around with it. Overall, I'm happy with the result of the latest release. Kudos to the contributors. Thanks.

GiteaMirror closed this issue

2025-11-11 14:04:36 -06:00

GiteaMirror commented

2025-11-11 14:04:37 -06:00

@tjbck commented on GitHub (Dec 13, 2023):

Hi, Thanks for the suggestion. RBAC is a feature that's being developed, stay tuned.

As for the all other numerous features you're requesting, I do not plan on adding them (non-core) in the near future, and will be only focusing on adding core features, so you would have to fork the repo and add features to the frontend and the backend yourself. Please refer to the code in the /src/lib and /src/routes for the frontend, /backend directory for the backend. Thanks. Duplicate of #68

@tjbck commented on GitHub (Dec 13, 2023): Hi, Thanks for the suggestion. RBAC is a feature that's being developed, stay tuned. As for the all other numerous features you're requesting, I do not plan on adding them (non-core) in the near future, and will be only focusing on adding core features, so you would have to fork the repo and add features to the frontend and the backend yourself. Please refer to the code in the `/src/lib` and `/src/routes` for the frontend, `/backend` directory for the backend. Thanks. Duplicate of #68

GiteaMirror commented

2025-11-11 14:04:37 -06:00

@turnercore commented on GitHub (Dec 24, 2023):

Hi, Thanks for the suggestion. RBAC is a feature that's being developed, stay tuned.

As for the all other numerous features you're requesting, I do not plan on adding them (non-core) in the near future, and will be only focusing on adding core features, so you would have to fork the repo and add features to the frontend and the backend yourself. Please refer to the code in the /src/lib and /src/routes for the frontend, /backend directory for the backend. Thanks. Duplicate of #68

Would you welcome PRs that add non-core features, or would you rather someone fork the project if they want to add non-core features?

@turnercore commented on GitHub (Dec 24, 2023): > Hi, Thanks for the suggestion. RBAC is a feature that's being developed, stay tuned. > > As for the all other numerous features you're requesting, I do not plan on adding them (non-core) in the near future, and will be only focusing on adding core features, so you would have to fork the repo and add features to the frontend and the backend yourself. Please refer to the code in the `/src/lib` and `/src/routes` for the frontend, `/backend` directory for the backend. Thanks. Duplicate of #68 Would you welcome PRs that add non-core features, or would you rather someone fork the project if they want to add non-core features?