mudler / mudler/LocalRecall

[Feature request] Default incompatibility adressing.

Open
#28 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
974
Forks
121
Avg merge
5h 52m
Merged PRs (30d)
1

Description

Greetings,

LocalAI default port is 8080, LocalRecall default port is 8080, yet it's assuming it's port of LocalAI...

Seems like madness.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue identifies a conflict between LocalAI and LocalRecall both using port 8080, but names no files, tests, or entry points. First locate where the LocalRecall and LocalAI default ports are configured and determine the intended non-conflicting behavior. Done means the defaults no longer assume the same port and the relevant behavior is verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.