cyberes
/
local-llm-server
Archived
1
1
Fork 0
Code Issues Pull Requests Packages Projects Releases 1 Wiki Activity
An HTTP API to serve local LLM Models.
This repository has been archived on 2024-10-27. You can view files and clone it, but cannot push or open issues or pull requests.
56 Commits 2 Branches 2 Tags 795 KiB
Python 92.3%
Shell 3.6%
HTML 3%
Dockerfile 0.7%
Jupyter Notebook 0.4%
Go to file
Cyberes 1cb6389a8a update gitignore 2023-08-24 00:10:22 -06:00
config update readme 2023-08-24 00:09:57 -06:00
llm_server update readme 2023-08-24 00:09:57 -06:00
other fix stats for real 2023-08-23 01:14:19 -06:00
templates update readme 2023-08-23 23:48:46 -06:00
.gitignore update gitignore 2023-08-24 00:10:22 -06:00
LICENSE Initial commit 2023-08-21 14:40:46 -06:00
README.md update readme 2023-08-24 00:09:57 -06:00
requirements.txt fix stats for real 2023-08-23 01:14:19 -06:00
server.py add dynamic analitics tracking to home page 2023-08-23 23:27:33 -06:00

README.md

local-llm-server

A HTTP API to serve local LLM Models.

The purpose of this server is to abstract your LLM backend from your frontend API. This enables you to make changes to (or even switch) your backend without affecting your clients.

Install

  1. sudo apt install redis
  2. python3 -m venv venv
  3. source venv/bin/activate
  4. pip install -r requirements.txt
  5. python3 server.py

An example systemctl service file is provided in other/local-llm.service.

Configure

First, set up your LLM backend. Currently, only oobabooga/text-generation-webui is supported, but eventually huggingface/text-generation-inference will be the default.

Then, configure this server. The config file is located at config/config.yml.sample so copy it to config/config.yml.

  1. Set backend_url to the base API URL of your backend.
  2. Set token_limit to the configured token limit of the backend. This number is shown to clients and on the home page.

To set up token auth, add rows to the token_auth table in the SQLite database.

token: the token/password.

type: the type of token. Currently unused (maybe for a future web interface?) but required.

priority: the lower this value, the higher the priority. Higher priority tokens are bumped up in the queue line.

uses: how many responses this token has generated. Leave empty.

max_uses: how many responses this token is allowed to generate. Leave empty to leave unrestricted.

expire: UNIX timestamp of when this token expires and is not longer valid.

disabled: mark the token as disabled.