Skip to main content

Install

To install FileFlows Forge, use this Docker Compose setup:

Docker Compose​

services:
fileflows-forge:
image: revenz/fileflows-forge
restart: unless-stopped
ports:
- 19201:19201
environment:
- TZ=Pacific/Auckland
volumes:
- ./data:/app/data

Settings Directory​

Forge stores all settings and data in a folder on your machine. The line ./fileflows-forge:/app/data tells Forge where to save this folder:

  • ./data ← This is on your machine (you can change this to any folder name you want, like ./my-forge-data)
  • :/app/data ← This stays the same (this is inside the container)

For example: ./my-forge-settings:/app/data or ./forge-data:/app/data. The folder will be created automatically.

Port Configuration​

The line 19201:19201 tells Docker how to access Forge on your machine:

  • Left side 19201 ← This is the port on your machine (this is what you change if you want Forge on a different port, like 9201 or 8888)
  • Right side 19201 ← This stays the same (this is inside the container)

So if you want Forge on port 9201, change it to: 9201:19201

Then you'd access Forge at: http://localhost:9201

Timezone​

Set the TZ value to your timezone. Only change the text after TZ=:

  • Default: TZ=Pacific/Auckland ← Change Pacific/Auckland
  • For New York: TZ=America/New_York
  • For London: TZ=Europe/London
  • For Sydney: TZ=Australia/Sydney
  • For UTC: TZ=UTC

Configure Forge​

To enable Forge services for your Flow Runners, configure the connection settings directly in the FileFlows Web Console. This allows flow elements to communicate with your Forge instance automatically.

Setup Instructions​

  1. Access Forge Settings: In the side navigation bar, scroll down to the Configuration section and select Forge.

  2. Forge URL: Enter the URL where Forge is hosted.

    • Example: http://10.0.0.123:19201
    • Note: If your Flow Runners are on different machines or in Docker containers, ensure you use an IP address accessible across your network.
  3. Forge Key: Enter your unique Forge Key. This key is used to authenticate the connection between FileFlows and the Forge server.

  4. Save: Click Save to apply the configuration.

Once saved, FileFlows will use these settings globally for any flow that requires Forge processing power.