# flow-pro

**Repository Path**: itmanvip/flow-pro

## Basic Information

- **Project Name**: flow-pro
- **Description**: No description available
- **Primary Language**: Unknown
- **License**: Not specified
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2026-07-21
- **Last Updated**: 2026-07-24

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

# Flow Pro

Flow Pro is a model-free workflow application with a Dify-compatible Vite web interface.

## Project layout

- `web`: Vite SPA frontend application
- `packages`: frontend workspace packages
- `java-api`: Java 8 workflow API with embedded GraalJS, port 5001
- `xxl-job-bridge`: Java 17/Spring Boot 4 adapter and XXL-JOB 3.4 executor, port 5002
- `源码/dify-main`: upstream Dify reference source only

GraalJS executes synchronously inside the workflow API JVM. Code nodes call the local Java service directly; no worker process or internal HTTP service is required.

## Build and test

```powershell
pnpm install --frozen-lockfile
pnpm --filter dify-web type-check
pnpm --filter dify-web build
mvn clean test
mvn -DskipTests package
```

XXL-JOB Bridge uses a separate JDK 17 toolchain:

```powershell
$env:JAVA_HOME='C:\path\to\jdk-17'
mvn -f xxl-job-bridge/pom.xml test
mvn -f xxl-job-bridge/pom.xml package
```

For production, build the frontend before packaging. Spring Boot embeds `web/dist` and serves both the SPA and API on port 5001:

```powershell
java -jar java-api/target/flow-pro-api-1.0.0-SNAPSHOT.jar
```

Open `http://localhost:5001/apps`.

For frontend development, keep the Java API running and start Vite separately:

```powershell
pnpm -C web dev
```

Open `http://localhost:3000/apps`.

## Capability contracts

- [Database connections and CRUD node](docs/DATABASE_CONNECTIONS.md)
- [Webhook triggers](docs/WEBHOOK_TRIGGERS.md)
- [MQ connections](docs/MQ_CONNECTIONS.md)
- [XXL-JOB Bridge API](docs/XXL_JOB_BRIDGE_API.md)
- [XXL-JOB distribution assessment](docs/XXL_JOB_DISTRIBUTION_COMPLIANCE.md)
- [Long-term implementation checklist](docs/LONG_TERM_IMPLEMENTATION_PLAN.md)

Database and MQ credentials use independent AES-GCM keyrings. Configure them before creating stored connections:

```powershell
$env:FLOW_PRO_DATABASE_CREDENTIAL_ACTIVE_KEY_ID='default'
$env:FLOW_PRO_DATABASE_CREDENTIAL_KEYS='default:<base64-encoded-16-24-or-32-byte-key>'
$env:FLOW_PRO_MQ_CREDENTIAL_ACTIVE_KEY_ID='default'
$env:FLOW_PRO_MQ_CREDENTIAL_KEYS='default:<base64-encoded-16-24-or-32-byte-key>'
```