No description
Find a file
kingbri 6c30f24c83 Tree: Unify sampler parameters and add override support
Unify API sampler params into a superclass which should make them
easier to manage and inherit generic functions from.

Not all frontends expose all sampling parameters due to connections
with OAI (that handles sampling themselves with the exception of
a few sliders).

Add the ability for the user to customize fallback parameters from
server-side.

In addition, parameters can be forced to a certain value server-side
in case the repo automatically sets other sampler values in the
background that the user doesn't want.

Signed-off-by: kingbri <bdashore3@proton.me>
2024-01-25 00:15:40 -05:00
.github/workflows feat: workflows for formatting/linting (#35) 2023-12-22 16:20:35 +00:00
backends/exllamav2 Tree: Refactor code organization 2024-01-25 00:15:40 -05:00
colab Tree: Refactor code organization 2024-01-25 00:15:40 -05:00
common Tree: Unify sampler parameters and add override support 2024-01-25 00:15:40 -05:00
docker Tree: Refactor code organization 2024-01-25 00:15:40 -05:00
loras Implement lora support (#24) 2023-12-08 23:38:08 -05:00
models Tree: Update documentation and configs 2023-11-16 02:30:33 -05:00
OAI Tree: Unify sampler parameters and add override support 2024-01-25 00:15:40 -05:00
sampler_overrides Tree: Unify sampler parameters and add override support 2024-01-25 00:15:40 -05:00
templates Templates: Update folder 2023-12-18 23:53:47 -05:00
tests Tree: Refactor code organization 2024-01-25 00:15:40 -05:00
.gitignore Tree: Unify sampler parameters and add override support 2024-01-25 00:15:40 -05:00
.ruff.toml feat: workflows for formatting/linting (#35) 2023-12-22 16:20:35 +00:00
config_sample.yml Tree: Unify sampler parameters and add override support 2024-01-25 00:15:40 -05:00
formatting.bat feat: workflows for formatting/linting (#35) 2023-12-22 16:20:35 +00:00
formatting.sh feat: workflows for formatting/linting (#35) 2023-12-22 16:20:35 +00:00
LICENSE Create LICENSE 2023-11-16 17:43:23 -05:00
main.py Tree: Unify sampler parameters and add override support 2024-01-25 00:15:40 -05:00
README.md Update README 2023-12-31 11:25:18 -05:00
requirements-amd.txt Requirements: Bump exllamav2 2024-01-22 21:13:31 -05:00
requirements-cu118.txt Requirements: Bump exllamav2 2024-01-22 21:13:31 -05:00
requirements-dev.txt feat: workflows for formatting/linting (#35) 2023-12-22 16:20:35 +00:00
requirements-nowheel.txt feat: logging (#39) 2023-12-23 04:33:31 +00:00
requirements.txt Requirements: Bump exllamav2 2024-01-22 21:13:31 -05:00
start.bat Tree: Format and cleanup start 2023-12-27 01:17:31 -05:00
start.py Tree: Refactor code organization 2024-01-25 00:15:40 -05:00
start.sh Start: Add shell script 2023-12-27 23:53:14 -05:00

TabbyAPI

Note

Need help? Join the Discord Server and get the Tabby role. Please be nice when asking questions.

A FastAPI based application that allows for generating text using an LLM (large language model) using the Exllamav2 backend

Disclaimer

This API is still in the alpha phase. There may be bugs and changes down the line. Please be aware that you might need to reinstall dependencies if needed.

Help Wanted

Please check the issues page for issues that contributors can help on. We appreciate all contributions. Please read the contributions section for more details about issues and pull requests.

If you want to add samplers, add them in the exllamav2 library and then link them to tabbyAPI.

Getting Started

Read the Wiki for more information. It contains user-facing documentation for installation, configuration, sampling, API usage, and so much more.

Supported Model Types

TabbyAPI uses Exllamav2 as a powerful and fast backend for model inference, loading, etc. Therefore, the following types of models are supported:

  • Exl2 (Highly recommended)

  • GPTQ

  • FP16 (using Exllamav2's loader)

Alternative Loaders/Backends

If you want to use a different model type than the ones listed above, here are some alternative backends with their own APIs:

Contributing

If you have issues with the project:

  • Describe the issues in detail

  • If you have a feature request, please indicate it as such.

If you have a Pull Request

  • Describe the pull request in detail, what, and why you are changing something

Developers and Permissions

Creators/Developers: