-
-
Notifications
You must be signed in to change notification settings - Fork 17.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
55cdf93
commit 13d69b7
Showing
14 changed files
with
182 additions
and
48 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
# 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` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,54 @@ | ||
version: '3.1' | ||
|
||
services: | ||
flowise: | ||
image: flowiseai/flowise | ||
restart: always | ||
environment: | ||
- PORT=${PORT} | ||
- CORS_ORIGINS=${CORS_ORIGINS} | ||
- IFRAME_ORIGINS=${IFRAME_ORIGINS} | ||
- FLOWISE_USERNAME=${FLOWISE_USERNAME} | ||
- FLOWISE_PASSWORD=${FLOWISE_PASSWORD} | ||
- FLOWISE_FILE_SIZE_LIMIT=${FLOWISE_FILE_SIZE_LIMIT} | ||
- DEBUG=${DEBUG} | ||
- DATABASE_PATH=${DATABASE_PATH} | ||
- DATABASE_TYPE=${DATABASE_TYPE} | ||
- DATABASE_PORT=${DATABASE_PORT} | ||
- DATABASE_HOST=${DATABASE_HOST} | ||
- DATABASE_NAME=${DATABASE_NAME} | ||
- DATABASE_USER=${DATABASE_USER} | ||
- DATABASE_PASSWORD=${DATABASE_PASSWORD} | ||
- DATABASE_SSL=${DATABASE_SSL} | ||
- DATABASE_SSL_KEY_BASE64=${DATABASE_SSL_KEY_BASE64} | ||
- APIKEY_STORAGE_TYPE=${APIKEY_STORAGE_TYPE} | ||
- APIKEY_PATH=${APIKEY_PATH} | ||
- SECRETKEY_PATH=${SECRETKEY_PATH} | ||
- FLOWISE_SECRETKEY_OVERWRITE=${FLOWISE_SECRETKEY_OVERWRITE} | ||
- LOG_LEVEL=${LOG_LEVEL} | ||
- LOG_PATH=${LOG_PATH} | ||
- BLOB_STORAGE_PATH=${BLOB_STORAGE_PATH} | ||
- DISABLE_FLOWISE_TELEMETRY=${DISABLE_FLOWISE_TELEMETRY} | ||
- MODEL_LIST_CONFIG_JSON=${MODEL_LIST_CONFIG_JSON} | ||
- GLOBAL_AGENT_HTTP_PROXY=${GLOBAL_AGENT_HTTP_PROXY} | ||
- GLOBAL_AGENT_HTTPS_PROXY=${GLOBAL_AGENT_HTTPS_PROXY} | ||
- GLOBAL_AGENT_NO_PROXY=${GLOBAL_AGENT_NO_PROXY} | ||
- DISABLED_NODES=${DISABLED_NODES} | ||
- MODE=${MODE} | ||
- WORKER_CONCURRENCY=${WORKER_CONCURRENCY} | ||
- QUEUE_NAME=${QUEUE_NAME} | ||
- QUEUE_REDIS_EVENT_STREAM_MAX_LEN=${QUEUE_REDIS_EVENT_STREAM_MAX_LEN} | ||
- REDIS_URL=${REDIS_URL} | ||
- REDIS_HOST=${REDIS_HOST} | ||
- REDIS_PORT=${REDIS_PORT} | ||
- REDIS_PASSWORD=${REDIS_PASSWORD} | ||
- REDIS_USERNAME=${REDIS_USERNAME} | ||
- REDIS_TLS=${REDIS_TLS} | ||
- REDIS_CERT=${REDIS_CERT} | ||
- REDIS_KEY=${REDIS_KEY} | ||
- REDIS_CA=${REDIS_CA} | ||
ports: | ||
- '${PORT}:${PORT}' | ||
volumes: | ||
- ~/.flowise:/root/.flowise | ||
entrypoint: /bin/sh -c "sleep 3; flowise worker" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters