dify/api
2024-10-18 15:05:27 +08:00
..
.idea
.vscode
configs chore: update MAX_VARIABLE_SIZE 2024-10-17 17:56:19 +08:00
constants
contexts
controllers chore: lint 2024-10-18 15:05:27 +08:00
core fix https://github.com/langgenius/dify/issues/9409 (#9433) 2024-10-17 10:47:56 +08:00
docker
events
extensions refactor: remove unnecessary 'closing' usage for boto3 client (#9343) 2024-10-15 08:42:39 +08:00
fields
libs Merge branch 'main' into feat/new-login-refresh-token 2024-10-14 10:25:18 +08:00
migrations
models
schedule update dataset clean rule (#9426) 2024-10-17 10:40:22 +08:00
services feat: add class variable 2024-10-18 11:42:14 +08:00
tasks feat: update mail template; 2024-10-18 14:16:14 +08:00
templates feat: update reset password template 2024-10-16 10:10:54 +08:00
tests feat: Enable baiduvector intergration test (#9369) 2024-10-16 09:41:28 +08:00
.dockerignore
.env.example Merge branch 'main' into feat/new-login-refresh-token 2024-10-14 10:25:18 +08:00
app.py Feat/implement-refresh-tokens (#9233) 2024-10-12 23:46:30 +08:00
commands.py feat:support baidu vector db (#9185) 2024-10-12 23:24:17 +08:00
Dockerfile
poetry.lock fix: Azure OpenAI o1 max_completion_token and get_num_token_from_messages error (#9326) 2024-10-15 16:26:44 +08:00
poetry.toml
pyproject.toml fix: Azure OpenAI o1 max_completion_token and get_num_token_from_messages error (#9326) 2024-10-15 16:26:44 +08:00
pytest.ini
README.md fix: poetry installation in CI jobs (#9336) 2024-10-14 22:22:03 +08:00

Dify Backend API

Usage

Important

In the v0.6.12 release, we deprecated pip as the package management tool for Dify API Backend service and replaced it with poetry.

  1. Start the docker-compose stack

    The backend require some middleware, including PostgreSQL, Redis, and Weaviate, which can be started together using docker-compose.

    cd ../docker
    cp middleware.env.example middleware.env
    # change the profile to other vector database if you are not using weaviate
    docker compose -f docker-compose.middleware.yaml --profile weaviate -p dify up -d
    cd ../api
    
  2. Copy .env.example to .env

  3. Generate a SECRET_KEY in the .env file.

    sed -i "/^SECRET_KEY=/c\SECRET_KEY=$(openssl rand -base64 42)" .env
    
    secret_key=$(openssl rand -base64 42)
    sed -i '' "/^SECRET_KEY=/c\\
    SECRET_KEY=${secret_key}" .env
    
  4. Create environment.

    Dify API service uses Poetry to manage dependencies. You can execute poetry shell to activate the environment.

  5. Install dependencies

    poetry env use 3.10
    poetry install
    

    In case of contributors missing to update dependencies for pyproject.toml, you can perform the following shell instead.

    poetry shell                                               # activate current environment
    poetry add $(cat requirements.txt)           # install dependencies of production and update pyproject.toml
    poetry add $(cat requirements-dev.txt) --group dev    # install dependencies of development and update pyproject.toml
    
  6. Run migrate

    Before the first launch, migrate the database to the latest version.

    poetry run python -m flask db upgrade
    
  7. Start backend

    poetry run python -m flask run --host 0.0.0.0 --port=5001 --debug
    
  8. Start Dify web service.

  9. Setup your application by visiting http://localhost:3000...

  10. If you need to handle and debug the async tasks (e.g. dataset importing and documents indexing), please start the worker service.

poetry run python -m celery -A app.celery worker -P gevent -c 1 --loglevel INFO -Q dataset,generation,mail,ops_trace,app_deletion

Testing

  1. Install dependencies for both the backend and the test environment

    poetry install --with dev
    
  2. Run the tests locally with mocked system environment variables in tool.pytest_env section in pyproject.toml

    cd ../
    poetry run -C api bash dev/pytest/pytest_all_tests.sh