[Script request]: Folding@home

[Sedation6612]

Application Name

Folding@home

Website

https://foldingathome.org/start-folding/

Description

A distrusted computing network that allows you to contribute your compute power to help fight global health threats like COVID19, Alzheimer’s Disease, and cancer.

Due Diligence

• I have searched existing scripts and found no duplicates.
• I have searched existing discussions and found no duplicate requests.
• The application requested has 200+ stars on Github (if applicable), is older than 6 months, actively maintained and has release tarballs published.

[007hacky007]

I picked this up and now have a tested Folding@Home LXC script working in my fork.

Tested branch:
https://github.com/007hacky007/ProxmoxVED/tree/foldingathome-v8-5-test

It currently includes:

• official Folding@Home v8.5 client install from Folding@Home’s package server
• amd64 and arm64 support
• optional account token + machine name prompt
• default CPU folding configuration
• CPU count set to all CPUs assigned to the LXC
• GPU passthrough support using the existing framework
• package-based update logic

I also opened a ProxmoxVED PR, but it was auto-closed by the new-script requirement checks:
community-scripts/ProxmoxVED#1692

The problem is that Folding@Home does not map cleanly to two of the automated criteria:

• 600+ GitHub stars
• official release tarballs are published

Folding@Home is an established project with official docs and package distribution, but the installable client packages are
hosted on Folding@Home’s own download infrastructure rather than GitHub releases:

• Project website: https://foldingathome.org/
• v8.5 guide: https://foldingathome.org/guides/v8-5-client-guide/
• FAQ: https://foldingathome.org/faqs/
• Official package source: https://download.foldingathome.org/releases/public/fah-client/
• Source repository: https://github.com/FoldingAtHome/fah-client-bastet

Would maintainers be open to a manual exception for this script so I can re-submit the PR for review?

[007hacky007]

@MickLesk could you please advise?

[CrazyWolf13]

@007hacky007 why do you ping tteck? He is sadly no longer with us.
tteck/Proxmox#4009

[007hacky007]

I did not know about that. I definitely did not want to cause any harm.

I don't know the whole history of the project. I just wanted to contribute with a code. Please accept my apologies.

[MickLesk]

community-scripts/ProxmoxVED#2318