Files
Flowise/docker
Lucas Mohallem Ferraz 1ae78c2739 [Feat] Allow AWS SECRETS MANAGER instead of storing AES Encrypted in db (#3616)
* AWS Secrets

* AWS Secrets support

* add examples

* remove test compose

* fix lint

* update aws secret manager implementation

* update secret manager client

* update comments

---------

Co-authored-by: Henry <hzj94@hotmail.com>
2025-01-08 20:24:57 +00:00
..
2024-09-19 18:38:43 +01:00
2024-07-12 17:57:58 +01:00

Flowise Docker Hub Image

Starts Flowise from DockerHub Image

Usage

  1. Create .env file and specify the PORT (refer to .env.example)
  2. docker compose up -d
  3. Open http://localhost:3000
  4. You can bring the containers down by docker compose stop

🔒 Authentication

  1. Create .env file and specify the PORT, FLOWISE_USERNAME, and FLOWISE_PASSWORD (refer to .env.example)
  2. Pass FLOWISE_USERNAME and FLOWISE_PASSWORD to the docker-compose.yml file:
    environment:
        - PORT=${PORT}
        - FLOWISE_USERNAME=${FLOWISE_USERNAME}
        - FLOWISE_PASSWORD=${FLOWISE_PASSWORD}
    
  3. docker compose up -d
  4. Open http://localhost:3000
  5. You can bring the containers down by docker compose stop

🌱 Env Variables

If you like to persist your data (flows, logs, apikeys, credentials), set these variables in the .env file inside docker folder:

  • DATABASE_PATH=/root/.flowise
  • APIKEY_PATH=/root/.flowise
  • LOG_PATH=/root/.flowise/logs
  • SECRETKEY_PATH=/root/.flowise
  • BLOB_STORAGE_PATH=/root/.flowise/storage

Flowise also support different environment variables to configure your instance. Read more