server: public: move default parameters to its own file#6858
server: public: move default parameters to its own file#6858xatier wants to merge 2 commits intoggml-org:masterfrom
Conversation
|
If you add a new file to |
|
@ngxson sorry, I'm not familiar with the code base, how do I do that? |
|
rebase. |
This commit enables users to easily update the parameters with desired default values without getting familiar with frontend details.
|
rebase. |
Sorry earlier I misunderstood your intent. I don't get how it will be easier for users without any knowledge about frontend details. You new js file is already part of frontend. Also I don't think many users want to change default params. At worst, we can implement a mechanism to save the params into localStorage to prevent it from being reset when user reload the page. But anw, I don't think it's needed for now; users who have problem with this part can always open an issue. |
|
@ngxson, I believe it's way easier for people to update values with my proposed Before my change, if one needs to update default values, they either need to do that on the UI each time, or try to decipher the complex Anyway, if you don't find it necessary, I can close the PR. |
This commit enables users to easily update the parameters with desired default values without getting familiar with frontend details.
Hi @ggerganov, very simple change, this commit allows users to configure and experiment with different parameters without patching the
index.htmleach time. I found it super helpful for my workflow (by swapping differentparams.jsfiles).