General
Language
The language that will be used in the system.
Debug Mode
When enabled, the web console will show extra debug information. This is useful for troubleshooting or inspecting app behaviour. Safe to leave off for most users.
Scan While Paused
When enabled, libraries will continue scanning even when the system is paused.
Queue Capacity
The maximum number of items that can be added to the queue. These include items that are out of schedule, on hold, or disabled. Increasing this number increases the data sent to the UI and may impact performance.
Max Page Size
The maximum number of items to display in a list. This applies to processed file data sent to the UI during loading. This number should be equal to or greater than the Queue Capacity.
Keep Failed Temp Files
Enabling this option will retain the temporary files used by a flow in case of failure, preventing them from being automatically deleted.
Temp Files for Moving/Copying
Use .fftemp files to avoid premature detection during move/copy.
DockerMods On Server
DockerMods should run automatically upon server startup or when specifically enabled. Otherwise, they will only execute when a flow is initiated.
Fenrus Dashboard Endpoint
Gives the processing status and storage savings to the Fenrus dashboard, and to any other dashboard or home page, at /webhook/fenrus. It is available without a license, and is off by default.
Turn it on, then give the dashboard the Endpoint URL and the Token. The token is sent with each call in one of these ways:
- the query string,
/webhook/fenrus?token=<token> - the
X-Webhook-Tokenheader - a bearer token,
Authorization: Bearer <token>
The endpoint only answers GET requests and returns JSON:
{
"Processing": 1,
"Failed": 0,
"Disabled": 0,
"OutOfSchedule": 0,
"Processed": 1234,
"Unprocessed": 56,
"UpdateAvailable": false,
"Libraries": [
{ "Library": "Movies", "TotalFiles": 100, "OriginalSize": 500000000000, "FinalSize": 300000000000 }
]
}
When it is off /webhook/fenrus returns a 404. Repeated calls with the wrong token block the caller's IP address for a while, as they do for Webhooks.
The route fenrus is reserved for this endpoint, a webhook cannot use it.
Telemetry
Telemetry helps us understand which devices to support, which Flow elements are most used, and where to focus development. All data is completely anonymous; no information about your actual filenames, file paths, or private data is ever collected or sent.
- Auto-Updates: Disabling telemetry also disables automatic updates, as checking our servers for updates inherently contacts fileflows.com.
- Opting Out: Anonymous telemetry is required for the free tier to help us sustainably maintain and improve the software. The option to completely disable telemetry is available as a benefit for users with an active license.
What We Collect
To be fully transparent, here is the exact list of anonymous data points sent by the app:
- Application Details: Software version, configured language, deployment method (e.g., Docker, Homebrew, systemd), and the database type used.
- System & Environment: Host operating system, system architecture, CPU/hardware specifications, and the number of active Agents (including their OS, architecture, and runner counts).
- Flow Statistics: An anonymous count of how often specific flow elements and scripts are utilized across your configurations.
- Processing Metrics: Total count of successfully processed files, failed files, the number of FileDrop users configured, and the total amount of disk storage space saved.