Closed vverma022 closed 1 month ago
Assign this issue to me. I'll resolve it.
A few queries:
Image 1
Image 2
Groq
or Grow
in the image 1?routes/ai_model_name.js
. For example, the readme mentions Cohere_API_Key
while cohere.js uses COHERE_API_KEY
. I've fixed this bug locally on my pc but haven't pushed it yet. If you're ok, I'll push it in the same branch that addresses this issue on node-modules?LLAMA_API_KEY
but the readme file mentions Groq_API_Key
. What to do about this?The Readme needs to be edited. Please use the variable names in the code base. I have not updated the readme.
The Readme needs to be edited. Please use the variable names in the code base. I have not updated the readme.
This answers the first three questions. What about question 4? Also, can you share the link to generate the api key for the env variable AI_ML_API_KEY?
The Readme needs to be edited. Please use the variable names in the code base. I have not updated the readme.
This answers the first three questions. What about question 4? Also, can you share the link to generate the api key for the env variable AI_ML_API_KEY?
Not integrated in the application as of now. But for reference https://aimlapi.com/app/sign-up/
The Readme needs to be edited. Please use the variable names in the code base. I have not updated the readme.
This answers the first three questions. What about question 4? Also, can you share the link to generate the api key for the env variable AI_ML_API_KEY?
Not integrated in the application as of now. But for reference https://aimlapi.com/app/sign-up/
Understood.
Just to be sure, is this the link to llama api?
The package.json in frontend/
does not have the start
script. How do I run the frontend of the application?
The package.json in
frontend/
does not have thestart
script. How do I run the frontend of the application?
Npm i to install the dependencies And then you can run npm run dev.
I've updated the readme on my branch. Review it
By the way, I fixed this backend/node_modules
issue. I just tested the application on my local pc and it is working fine. Shall I merge it into main on my fork and then create a pull request?
Please create a pull request.
I created a pull request. Review and let me know regarding any changes.
Since you merged the pull request, I think this issue can be closed now.
The issue that I am facing right now concerns with node_modules not being ignored despite adding
node_modules
tobackend/.gitignore
file. As the new files innode_modules
are being tracked by git, I can't make a sensible commit.Originally posted by @NatsuDrag9 in https://github.com/vverma022/model-merge/issues/6#issuecomment-2229964559