[PR #38] [MERGED] New Script: FileFlows #849

Closed
opened 2025-09-09 19:48:10 -05:00 by giteasync · 0 comments

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVED/pull/38
Author: @kkroboth
Created: 3/12/2025
Status: Merged
Merged: 3/19/2025
Merged by: @MickLesk

Base: mainHead: lxc-fileflows


📝 Commits (10+)

  • a898a37 chore: json info
  • 17125a4 feat: fileflows ct and install
  • 0a2722e fix: update build.func link
  • 9ff05c6 fix: hardware accel and naming issues
  • 8d22ce9 chore: fileflows update script
  • 5d189e5 test: update misc links
  • dfe9980 fix: use built-in systemd installer
  • cb95b41 chore: update multimedia keys
  • 7691f65 fix: use non-free intel va driver
  • 5f1f6d3 fix: quiet logs and remove duplicate service install

📊 Changes

4 files changed (+186 additions, -2 deletions)

View changed files

ct/fileflows.sh (+73 -0)
install/fileflows-install.sh (+72 -0)
json/fileflows.json (+39 -0)
📝 misc/build.func (+2 -2)

📄 Description

✍️ Description

FileFlows is a powerful, open-source tool for automating media file processing workflows, including encoding, decoding, and media management. It offers an intuitive GUI and extensive plugin support, making it ideal for tasks like video transcoding, organizing, and managing large media libraries.

https://github.com/community-scripts/ProxmoxVE/discussions/324

Prerequisites

Before this PR can be reviewed, the following must be completed:

  • Self-review performed – Code follows established patterns and conventions.
  • Testing performed – Changes have been thoroughly tested and verified.

🛠️ Type of Change

Select all that apply:

  • 🆕 New script – A fully functional and tested script or script set.
  • [] 🐞 Bug fix – Resolves an issue without breaking functionality.
  • New feature – Adds new, non-breaking functionality.
  • [] 💥 Breaking change – Alters existing functionality in a way that may require updates.

📋 Additional Information (optional)

FileFlows is still new to me, but I wanted this cleaner interface compared to Tdarr. Maybe @GCustom, @kalua85, and @leah-potato can take a look as you were all on the original discussion thread.

This script does check if the LXC container is privileged and will set up HW Acceleration just like our Jellyfin, Tdarr, ErsatzTV, and others do. I did add the option to install the intel-media-va-driver-non-free by asking the user Y/N during installation. I copied that portion from https://github.com/community-scripts/ProxmoxVED/blob/main/misc/hw-acceleration.sh. At least with my home-lab setup, only the non-free driver worked for me.

I'm still hesitant on keeping the update function because I couldn't find a reliable way to check for updates on git or their website. It's a freemium software just like Tdarr. Looking at the self-hosted service's API, I did find endpoints to check if there's an update. I did my best to check and then extract the latest version. If that isn't fine, I can take the update script out. FileFlows does have an auto-updater, but that's in their basic subscription (non-free). I believe the app should tell you there's an update and it can do it manually.

The other gotcha was setting up the correct ffmpeg and ffmprobe paths. FileFlows expects them to be in /usr/local/bin, but ffmpeg installs it at /usr/bin. Since FileFlows doesn't have an config file to edit those variables, I had to use the API endpoints to delete, then re-add them under the new paths.

New feature

I had to modify the build.func to include this new script FileFlows during the HW Acceleration setup.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/community-scripts/ProxmoxVED/pull/38 **Author:** [@kkroboth](https://github.com/kkroboth) **Created:** 3/12/2025 **Status:** ✅ Merged **Merged:** 3/19/2025 **Merged by:** [@MickLesk](https://github.com/MickLesk) **Base:** `main` ← **Head:** `lxc-fileflows` --- ### 📝 Commits (10+) - [`a898a37`](https://github.com/community-scripts/ProxmoxVED/commit/a898a373d55b6bea5f1ca5038eefb5a917488a44) chore: json info - [`17125a4`](https://github.com/community-scripts/ProxmoxVED/commit/17125a45bd4255a85bbb8a0861a3993e240f7a59) feat: fileflows ct and install - [`0a2722e`](https://github.com/community-scripts/ProxmoxVED/commit/0a2722ee95bf7d685989d116fba60cd49d8e7e3a) fix: update build.func link - [`9ff05c6`](https://github.com/community-scripts/ProxmoxVED/commit/9ff05c6cc9f805eb7bddff82f8eddb12ca272bdb) fix: hardware accel and naming issues - [`8d22ce9`](https://github.com/community-scripts/ProxmoxVED/commit/8d22ce9ba9d11d3768f9a83b0a397a4cf70c4383) chore: fileflows update script - [`5d189e5`](https://github.com/community-scripts/ProxmoxVED/commit/5d189e5d604592d59146eea43debf9e887ba3399) test: update misc links - [`dfe9980`](https://github.com/community-scripts/ProxmoxVED/commit/dfe9980f09676777e0047fdb56bb2523cbba82e0) fix: use built-in systemd installer - [`cb95b41`](https://github.com/community-scripts/ProxmoxVED/commit/cb95b41f9217efbda8f6f6f91c995ad58c94d942) chore: update multimedia keys - [`7691f65`](https://github.com/community-scripts/ProxmoxVED/commit/7691f655fc4cf944f78d748d7c498a9f66cc1c8d) fix: use non-free intel va driver - [`5f1f6d3`](https://github.com/community-scripts/ProxmoxVED/commit/5f1f6d3684aa73e3b402bae906ea07952b1882ac) fix: quiet logs and remove duplicate service install ### 📊 Changes **4 files changed** (+186 additions, -2 deletions) <details> <summary>View changed files</summary> ➕ `ct/fileflows.sh` (+73 -0) ➕ `install/fileflows-install.sh` (+72 -0) ➕ `json/fileflows.json` (+39 -0) 📝 `misc/build.func` (+2 -2) </details> ### 📄 Description ## ✍️ Description [FileFlows](https://fileflows.com/) is a powerful, open-source tool for automating media file processing workflows, including encoding, decoding, and media management. It offers an intuitive GUI and extensive plugin support, making it ideal for tasks like video transcoding, organizing, and managing large media libraries. ## 🔗 Related PR / Discussion / Issue https://github.com/community-scripts/ProxmoxVE/discussions/324 ## ✅ Prerequisites Before this PR can be reviewed, the following must be completed: - [x] **Self-review performed** – Code follows established patterns and conventions. - [x] **Testing performed** – Changes have been thoroughly tested and verified. ## 🛠️ Type of Change Select all that apply: - [x] 🆕 **New script** – A fully functional and tested script or script set. - [] 🐞 **Bug fix** – Resolves an issue without breaking functionality. - [x] ✨ **New feature** – Adds new, non-breaking functionality. - [] 💥 **Breaking change** – Alters existing functionality in a way that may require updates. ## 📋 Additional Information (optional) FileFlows is still new to me, but I wanted this cleaner interface compared to Tdarr. Maybe @GCustom, @kalua85, and @leah-potato can take a look as you were all on the original discussion thread. This script does check if the LXC container is privileged and will set up HW Acceleration just like our Jellyfin, Tdarr, ErsatzTV, and others do. I did add the option to install the `intel-media-va-driver-non-free` by asking the user Y/N during installation. I copied that portion from https://github.com/community-scripts/ProxmoxVED/blob/main/misc/hw-acceleration.sh. At least with my home-lab setup, only the `non-free` driver worked for me. I'm still hesitant on keeping the update function because I couldn't find a reliable way to check for updates on git or their website. It's a freemium software just like Tdarr. Looking at the self-hosted service's API, I did find endpoints to check if there's an update. I did my best to check and then extract the latest version. If that isn't fine, I can take the update script out. FileFlows does have an auto-updater, but that's in their basic subscription (non-free). I believe the app should tell you there's an update and it can do it manually. The other gotcha was setting up the correct `ffmpeg` and `ffmprobe` paths. FileFlows expects them to be in `/usr/local/bin`, but ffmpeg installs it at `/usr/bin`. Since FileFlows doesn't have an config file to edit those variables, I had to use the API endpoints to delete, then re-add them under the new paths. ### ✨ **New feature** I had to modify the `build.func` to include this new script `FileFlows` during the HW Acceleration setup. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
giteasync added the pull-request label 2025-09-09 19:48:10 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: community-scripts/ProxmoxVED#849