FlowiseAI/Flowise.git:

代码拉取完成,页面将自动刷新

扫描微信二维码支付

取消

支付完成

richgiteeai

Watch

不关注关注所有动态仅关注版本发行动态关注但不提醒动态

1 Star 0 Fork 0

Samle/Flowise

代码 Issues 0 Pull Requests 0 Wiki 统计流水线

服务

加入 Gitee

与超过 1400万开发者一起发现、参与优秀开源项目,私有仓库也完全免费 :)

免费加入

已有帐号? 立即登录

文件

新建文件新建 Diagram 文件

main

分支 (528)

标签 (246)

管理

main

fix/nvidia-nim

fix/nim-container-manager

feature/Agentflow-V2

customCallback

release/2.2.7-patch.1

chore/BullMQ-Version-Upgrade

bugfix/Post-API-Chain-URL

bugfix/Arbitrary-File-Upload

bugfix/S3-Credentials

chore/Synax-Highlight-bug

chore/Dev-Setup

feature/MCP

release/2.2.7

feature/Composio-Multi-Select

release/2.2.6-hotfix.1

release/2.2.6

feature/NIM-Container

bugfix/Custom-Tool-Date-Type

chore/Patch-Dependencies

flowise-ui@2.2.7-patch.1

flowise@2.2.7-patch.1

flowise-components@2.2.7-patch.1

flowise-components@2.2.7

flowise-ui@2.2.7

flowise@2.2.7

flowise@2.2.6-hotfix.1

flowise-components@2.2.6

flowise-ui@2.2.6

flowise@2.2.6

flowise-components@2.2.5

flowise-ui@2.2.5

flowise@2.2.5

flowise-components@2.2.4

flowise-ui@2.2.4

flowise@2.2.4

flowise-components@2.2.3

flowise-ui@2.2.3

flowise@2.2.3

flowise-components@2.2.2

克隆/下载

HTTPS SSH SVN SVN+SSH 下载ZIP

提示

下载代码请复制以下命令到终端执行

为确保你提交的代码身份被 Gitee 正确识别,请执行以下命令完成配置

git config --global user.name userName 
git config --global user.email userEmail

初次使用 SSH 协议进行代码克隆、推送等操作时,需按下述提示完成 SSH 配置

1 生成 RSA 密钥

2 获取 RSA 公钥内容,并配置到 SSH公钥中

在 Gitee 上使用 SVN,请访问使用指南

使用 HTTPS 协议时,命令行会出现如下账号密码验证步骤。基于安全考虑,Gitee 建议配置并使用私人令牌替代登录密码进行克隆、推送等操作

Username for 'https://gitee.com': userName

Password for 'https://userName@gitee.com': # 私人令牌

新建文件新建 Diagram 文件

分支 528

标签 246

贡献代码

同步代码

创建 Pull Request

了解更多

对比差异通过 Pull Request 同步

同步更新到分支

通过 Pull Request 同步

将会在向当前分支创建一个 Pull
Request,合入后将完成同步

Henry Heng Feature/Add bullmq redis for message queue... a2a475b

2875 次提交

File empty ...

README.md

docker-compose.yml

README

# Flowise Worker

By utilizing worker instances when operating in queue mode, Flowise can be scaled horizontally by adding more workers to handle increased workloads or scaled down by removing workers when demand decreases.

Here’s an overview of the process:

1. The primary Flowise instance sends an execution ID to a message broker, Redis, which maintains a queue of pending executions, allowing the next available worker to process them.
2. A worker from the pool retrieves a message from Redis.
 The worker starts execute the actual job.
3. Once the execution is completed, the worker alerts the main instance that the execution is finished.

# How to use

## Setting up Main Server:

1. Follow [setup guide](https://github.com/FlowiseAI/Flowise/blob/main/docker/README.md)
2. In the `.env.example`, setup all the necessary env variables for `QUEUE CONFIGURATION`

## Setting up Worker:

1. Copy paste the same `.env` file used to setup main server. Change the `PORT` to other available port numbers. Ex: 5566
2. `docker compose up -d`
3. Open [http://localhost:5566](http://localhost:5566)
4. You can bring the worker container down by `docker compose stop`