Originally created by @tmc on GitHub (May 1, 2024).
I really enjoyed this project most when it could simply be a frontend for ollama. Please make it an option to reduce complexity and not require a backend process.
npm i; npm run dev -> working UI was wonderfully easy, and this has been lost.
Originally created by @tmc on GitHub (May 1, 2024).
I really enjoyed this project most when it could simply be a frontend for ollama. Please make it an option to reduce complexity and not require a backend process.
`npm i; npm run dev` -> working UI was wonderfully easy, and this has been lost.
I didn't get to use it back then, basically are you saying that you just connected the front end to some external API and then used it as a thin-client. Cuz if so that would actually be pretty sweet and I'd second that kind of capability
@skyler14 commented on GitHub (May 1, 2024):
I didn't get to use it back then, basically are you saying that you just connected the front end to some external API and then used it as a thin-client. Cuz if so that would actually be pretty sweet and I'd second that kind of capability
To clarify, our goal is to enable a frontend-only build within our existing codebase, without the need to create a separate project and remove all backend code permanently. An ideal solution would be a build-time flag for the frontend that disables backend-dependent functionality.
Additionally, this flag should save all preferences and settings to LocalStorage and allow Ollama/OpenAI API calls to be sent directly, bypassing the need for backend proxying. This will allow for a more streamlined and efficient frontend-only build based off the same codebase.
@justinh-rahb commented on GitHub (May 1, 2024):
> Not on the short term roadmap but PR welcome!
To clarify, our goal is to enable a frontend-only build within our existing codebase, without the need to create a separate project and remove all backend code permanently. An ideal solution would be a build-time flag for the frontend that disables backend-dependent functionality.
Additionally, this flag should save all preferences and settings to LocalStorage and allow Ollama/OpenAI API calls to be sent directly, bypassing the need for backend proxying. This will allow for a more streamlined and efficient frontend-only build based off the same codebase.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @tmc on GitHub (May 1, 2024).
I really enjoyed this project most when it could simply be a frontend for ollama. Please make it an option to reduce complexity and not require a backend process.
npm i; npm run dev-> working UI was wonderfully easy, and this has been lost.@skyler14 commented on GitHub (May 1, 2024):
I didn't get to use it back then, basically are you saying that you just connected the front end to some external API and then used it as a thin-client. Cuz if so that would actually be pretty sweet and I'd second that kind of capability
@tjbck commented on GitHub (May 1, 2024):
Not on the short term roadmap but PR welcome!
@justinh-rahb commented on GitHub (May 1, 2024):
To clarify, our goal is to enable a frontend-only build within our existing codebase, without the need to create a separate project and remove all backend code permanently. An ideal solution would be a build-time flag for the frontend that disables backend-dependent functionality.
Additionally, this flag should save all preferences and settings to LocalStorage and allow Ollama/OpenAI API calls to be sent directly, bypassing the need for backend proxying. This will allow for a more streamlined and efficient frontend-only build based off the same codebase.