Linux

Prerequisites

.NET 10 SDK

For detailed instructions how to install .NET on linux refer to this guide from Microsoft.

FFmpeg

If you wish to use the Video Plugin to process videos, you must install FFmpeg on your system.

---

FileFlows Downloads

No downloads available.

---

Scripted Install

Server

Install and run FileFlows

wget -O FileFlows.tar.xz https://fileflows.com/downloads/tarxz
mkdir -p FileFlows && tar -xJf FileFlows.tar.xz -C FileFlows
cd FileFlows/
chmod +x run-server.sh
./run-server.sh

This will launch the server with a GUI. To launch it without a GUI, use cd Server

dotnet FileFlows.Server.dll

info

You should now be able to view FileFlows in the browser on http://localhost:19200/

In order for plugins to find the FFmpeg tool, it must be added under the Variables page.

Name	Value	Description
Name	ffmpeg	The name of the variable, this is case insensitive
Path	/usr/bin/ffmpeg	The path to your ffmpeg instance

Agent

Running the Agent

You can start the FileFlows Agent using the runner script or directly from the Agent directory.

If agent.config does not exist when running the application, it will automatically be created.

Option 1: Using the Runner Script

If your server URL is already configured in agent.config:

./run-agent.sh

If you haven't configured agent.config, pass the server URL as the first parameter:

./run-agent.sh http://fileflows:19200/

---

Option 2: Running Directly

If your server URL is already configured in agent.config:

cd Agent
dotnet FileFlows.Agent.dll

If you haven't configured agent.config, pass the server URL using the --server flag:

cd Agent
dotnet FileFlows.Agent.dll --server http://fileflows:19200/

---

Configuration File Setup

Alternatively, you can pre-configure or edit the server URL in agent.config so you don't need to pass command-line parameters on launch. The file will automatically be created on first run if it does not exist:

Data/agent.config

{
  "ServerUrl": "http://fileflows:19200/",
  "AccessToken": "",
  "StartMinimized": false,
  "HostName": "fedora"
}

note

Replace http://fileflows:19200/ with the actual address and port of your FileFlows Server.