Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-20 06:33:42 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #4] Coding Support #3

New Issue
Closed
opened 2026-02-22 18:17:23 -05:00 by yindo · 4 comments
yindo commented 2026-02-22 18:17:23 -05:00
Owner
Copy Link
Copy Source

Originally created by @mkammes on GitHub (Jun 8, 2023).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4

First off, this project looks extraordinarily useful!

If a user wanted help debugging code - or prototyping apps - what would be the best way to handle this? Push to a github repo for the LLM to index, or perhaps flatten code into a PDF?

Keep up the good work!

Originally created by @mkammes on GitHub (Jun 8, 2023). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4 First off, this project looks extraordinarily useful! If a user wanted help debugging code - or prototyping apps - what would be the best way to handle this? Push to a github repo for the LLM to index, or perhaps flatten code into a PDF? Keep up the good work!
yindo closed this issue 2026-02-22 18:17:23 -05:00
yindo commented 2026-02-22 18:17:23 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jun 8, 2023):

Oh you mean being able to consume code as a file? I would think it could be recursively possible using the langchain git loader or some other tool.

I would think right now it would be best to export these as .txt files with their line numbers for each file.

@timothycarambat commented on GitHub (Jun 8, 2023): Oh you mean being able to consume code as a file? I would think it could be recursively possible using the langchain `git` loader or some other tool. I would think right now it would be best to export these as .txt files with their line numbers for each file.
yindo commented 2026-02-22 18:17:23 -05:00
Author
Owner
Copy Link
Copy Source

@martinsantos commented on GitHub (Jun 8, 2023):

Error: Failed to fetch

in WORKSPACE creation?

@martinsantos commented on GitHub (Jun 8, 2023): Error: Failed to fetch in WORKSPACE creation?
yindo commented 2026-02-22 18:17:23 -05:00
Author
Owner
Copy Link
Copy Source

@kichen1984 commented on GitHub (Jun 8, 2023):

Same as above. Getting a failed to fetch error on localhost:5000/workspaces. The settings tab gives an error "ENV settings are missing - this software will not function fully.". I'm using Chroma, commented out Pinecone and uncommented the Chroma section for clarity. When starting the server I'm also getting...

"[nodemon] watching extensions: js,mjs,json
[nodemon] starting node --trace-warnings index.js
[nodemon] clean exit - waiting for changes before restart"

When you attempt to yarn dev:frontend after that it opens the frontend on port 3000 and restricts any update to settings in the vite dev environment.

So close, any help is appreciated.

@kichen1984 commented on GitHub (Jun 8, 2023): Same as above. Getting a failed to fetch error on localhost:5000/workspaces. The settings tab gives an error "ENV settings are missing - this software will not function fully.". I'm using Chroma, commented out Pinecone and uncommented the Chroma section for clarity. When starting the server I'm also getting... "[nodemon] watching extensions: js,mjs,json [nodemon] starting `node --trace-warnings index.js` [nodemon] clean exit - waiting for changes before restart" When you attempt to yarn dev:frontend after that it opens the frontend on port 3000 and restricts any update to settings in the vite dev environment. So close, any help is appreciated.
yindo commented 2026-02-22 18:17:23 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jun 8, 2023):

@kichen1984 @martinsantos Open a new issue when you issue is unrelated to the current topic.

@kichen1984 this is what your server/.env.development should look like

SERVER_PORT=5000
OPEN_AI_KEY=your-open-ai-api-key
OPEN_MODEL_PREF='gpt-3.5-turbo'
CACHE_VECTORS="true"

# Enable all below if you are using vector database: Chroma.
VECTOR_DB="chroma"
CHROMA_ENDPOINT='http://localhost:8000'

it is also possible there is another instance of the server running so run sh clean.sh after exiting the server to ensure the port is released when updating the .env because nodemon sometimes will not release it.

@timothycarambat commented on GitHub (Jun 8, 2023): @kichen1984 @martinsantos Open a new issue when you issue is unrelated to the current topic. @kichen1984 this is what your `server/.env.development` should look like ``` SERVER_PORT=5000 OPEN_AI_KEY=your-open-ai-api-key OPEN_MODEL_PREF='gpt-3.5-turbo' CACHE_VECTORS="true" # Enable all below if you are using vector database: Chroma. VECTOR_DB="chroma" CHROMA_ENDPOINT='http://localhost:8000' ``` it is also possible there is another instance of the server running so run `sh clean.sh` after exiting the server to ensure the port is released when updating the .env because nodemon sometimes will not release it.
yindo changed title from Coding Support to [GH-ISSUE #4] Coding Support 2026-06-05 14:32:55 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#3
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?