docs: update documentation to reflect by default enabling of --webserver in 0.11

This commit is contained in:
Meng Zhang 2024-05-10 15:31:26 -07:00
parent a112b85ae7
commit f719eed9bb
4 changed files with 4 additions and 6 deletions

View File

@ -98,7 +98,7 @@ Tabby is broken up into several crates, each responsible for a different part of
- `crates/tabby-scheduler` - Defines jobs that need to run periodically for syncing and indexing code
- `crates/tabby-inference` - Defines interfaces for interacting with text generation models
- `crates/llama-cpp-bindings` - Raw bindings to talk with the actual models in C++ from Rust
- `ee/tabby-webserver` - The webserver for Tabby with privilege management and a chatbot playground. Also includes GraphQL API implementation. Must use `--webserver` on CLI to enable
- `ee/tabby-webserver` - The webserver for Tabby with privilege management and a chatbot playground. Also includes GraphQL API implementation.
- `ee/tabby-db` - The database backing the webserver
- `ee/tabby-ui` - Frontend for the Tabby webserver

View File

@ -1,5 +1,4 @@
//! Defines behavior for the tabby webserver which allows users to interact with enterprise features.
//! Using the web interface (e.g chat playground) requires using this module with the `--webserver` flag on the command line.
mod dao;
mod env;
mod schema;

View File

@ -1,5 +1,4 @@
//! Defines behavior for the tabby webserver which allows users to interact with enterprise features.
//! Using the web interface (e.g chat playground) requires using this module with the `--webserver` flag on the command line.
mod axum;
mod hub;
mod jwt;

View File

@ -9,12 +9,12 @@ This feature is available in the **Team** and **Enterprise** Plans.
Tabby provides built-in distributed support for multi-node setups. This allows you to scale your Tabby deployment horizontally and distribute the workload across multiple GPU workers.
## Start the Webserver
## Start Tabby
Start the web server using the following command:
Start the web UI using the following command:
```bash
tabby serve --webserver
tabby serve
```
By doing so, the web server will operate without a model attached to it. If you send a POST request to `/v1/completions`, you will receive a `501 Not Implemented` error.