You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
gcgj-dify-1.7.0/api
keita69 cdc2a6f637
The firecrawl tool now supports self-hosting (#5528)
Co-authored-by: takatost <takatost@gmail.com>
2 years ago
..
configs chore: use singular style in middleware config class name (#5502) 2 years ago
constants feat: make Citations and Attributions display enable default (#5508) 2 years ago
controllers fix: revert CI path filters (#5561) 2 years ago
core The firecrawl tool now supports self-hosting (#5528) 2 years ago
docker feat: add `flask upgrade-db` command for running db upgrade with redis lock (#5333) 2 years ago
events feat: support opensearch approximate k-NN (#5322) 2 years ago
extensions feat: introduce pydantic-settings for config definition and validation (#5202) 2 years ago
fields feat: option to hide workflow steps (#5436) 2 years ago
libs feat(api/auth): switch-to-stateful-authentication (#5438) 2 years ago
migrations refactor: extract db configs and celery configs into dify config (#5491) 2 years ago
models feat: make Citations and Attributions display enable default (#5508) 2 years ago
schedule Feat/dify rag (#2528) 2 years ago
services fix: correct typos (#5510) 2 years ago
tasks Feat/firecrawl data source (#5232) 2 years ago
templates fix: email template style (#1914) 2 years ago
tests chore: refactor the http executor node (#5212) 2 years ago
.dockerignore build: support Poetry for depencencies tool in api's Dockerfile (#5105) 2 years ago
.env.example add opensearch default value (#5536) 2 years ago
Dockerfile fix: apply best practices for the latest buildkit (#5527) 2 years ago
README.md chore: remove pip support for api service (#5453) 2 years ago
app.py chore: use singular style in config class name (#5489) 2 years ago
commands.py feat: support opensearch approximate k-NN (#5322) 2 years ago
config.py feat: Add program_name attribute to TiDB connection (#5499) 2 years ago
poetry.lock Add Oracle23ai as a vector datasource (#5342) 2 years ago
poetry.toml build: initial support for poetry build tool (#4513) 2 years ago
pyproject.toml Add Oracle23ai as a vector datasource (#5342) 2 years ago
requirements.txt chore: remove pip support for api service (#5453) 2 years ago

README.md

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
    docker-compose -f docker-compose.middleware.yaml -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 debug local async processing, please start the worker service.

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

The started celery app handles the async tasks, e.g. dataset importing and documents indexing.

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