Linux Installation

Prerequisites

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

Install .NET 6 (Ubuntu)

Add Microsoft package signing key to your list of trusted keys

wget https://packages.microsoft.com/config/ubuntu/16.04/packages-microsoft-prod.deb -O packages-microsoft-prod.deb
sudo dpkg -i packages-microsoft-prod.deb
rm packages-microsoft-prod.deb

Install dotnet

sudo apt-get update; \
  sudo apt-get install -y apt-transport-https && \
  sudo apt-get update && \
  sudo apt-get install -y aspnetcore-runtime-6.0

Test dotnet is installed by running dotnet and confirming

> dotnet

Usage: dotnet [options]
Usage: dotnet [path-to-application]

Options:
  -h|--help         Display help.
  --info            Display .NET information.
  --list-sdks       Display the installed SDKs.
  --list-runtimes   Display the installed runtimes.

path-to-application:
  The path to an application .dll file to execute.

FFMPEG

If you wish to use the Video Nodes to process videos, you must download FFMPEG for your system.

apt-get install ffmpeg

Server

Install and run FileFlows

wget -O FileFlows.zip https://fileflows.com/downloads/zip
unzip FileFlows.zip -d FileFlows
cd FileFlows/
chmod +x run-server.sh
sudo ./run-server.sh

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

sudo dotnet FileFlows.Server.dll --no-gui true

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

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

Open the FileFlows UI on http://localhost:5000/ Navigate to the “Variables” Page Edit the “ffmpeg”, if not there click “Add” and add it Enter | Name | Variable | Description | | :—: | :—: | :—: | | Name | ffmpeg | The name of the variable, this is case insensitive | | Path | /usr/bin/ffmpeg | The path to your ffmpeg instance |

Click “Save”


Node

NOTE: Replace [SERVER_ADDRESS] with the FileFlows Server address you are connecting to. For example http://tower:5000/

wget -O FileFlows.zip https://fileflows.com/downloads/zip
unzip FileFlows.zip -d FileFlows
cd FileFlows
chmod +x run-node.sh
sudo ./run-node.sh

This will launch the FileFlows node GUI. You can optionally specify the server address

cd Node
sudo dotnet FileFlows.Node.dll --server [SERVER_ADDRESS] --no-gui

If you omit the –server variable, FileFlows.Node will look for fileflow.config file and read the server information from there. If that file is missing, a new one will be created and the process will exit, or if no server is defined in that file the process will exit. With the fileflows.config file correctly configured, there is no need to specify the server via the –server switch

FileFlows Server Configuration

Now that the FileFlows Node is up and running you need to configure some mappings in FileFlows Server.

These mappings let FileFlows map from a Server path/application to one local to the Node.

Open FileFlows server application UI, go to “Nodes” and edit the node.

Server Node Description
/usr/local/bin/ffmpeg /usr/local/bin/ffmpeg TThe FFMPEG instance on the Server and the Node, this example demostrates a docker setup.
/media/movies /mnt/server/media/movies This is an example mapping for a library
© 2022 FileFlows