2.3.31 Satellite: Flowise

Flowise

Handle: flowise
URL: http://localhost:34281

Open source low-code tool for developers to build customized LLM orchestration flow & AI agents.

Starting

# [Optional] Pre-pull the image
harbor pull flowise

# Start the service [--open is optional, to auto open in browser]
harbor up flowise --open

Usage

Flowise connections are mostly configured specifically for a given workflow right within the nodes.

When running alongside other services in Harbor - use their internal URLs. For example:

# Ollama URL for the Flowise
harbor url -i ollama

Here's the most basic chat workflow:

Other than that, Flowise is an extremely feature-rich tool with a lot of capabilities, please see the official documentation and tutorials to get started.

Configuration

Official environment variables reference. To set them, see Harbor's environment configuration guide.

Apart from that, you can configure the following via harbor config with the following options supported:

# The port on the host machine to access
# the Flowise service API and UI
HARBOR_FLOWISE_HOST_PORT       34281

# The Docker image to use
HARBOR_FLOWISE_IMAGE           flowiseai/flowise
# The tag of the Docker image to use
HARBOR_FLOWISE_VERSION         3.1.3

# Location of the workspace directory on the host machine
# relative to $(harbor home), but can be global as well
HARBOR_FLOWISE_WORKSPACE       ./services/flowise/data

Note

The version is pinned to 3.1.3 — 3.1.4 and current latest crash at startup (upstream session-store bug: a filename string is passed where the vendored connect-sqlite3 expects an open database handle).

Flowise runs as the host user and persists its data at /home/node/.flowise inside the container (mapped to HARBOR_FLOWISE_WORKSPACE), so files in the workspace stay owned by your host user.