DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to add extra runner machines to a self-hosted FDE Gym site with Fde Gym

Attach more machines to run cases, on any network that reaches the site.

Authorization notice. Fde Gym is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forAn operator of a team FDE Gym site whose runs are queuing or whose cases need more capacity than one machine provides.

The problemA single runner can become a bottleneck when many people work cases at once, and the site needs more machines without sharing its database or keys.

The outcomeAdditional runners attached to the site, with a clear record of which machine runs which case work.

What you need first

  • Docker
  • Python 3.9 or later
  • An OpenRouter key, stored in a file outside the repository
  • Git

Steps

  1. Read docs/self-hosting.md and its section on adding machines to run cases on.
  2. On a second machine, follow the runner setup in docs/self-hosting.md so it can reach the site over the network. (inferred, check the README)
  3. Confirm the new runner appears in the admin console's machines list.
  4. Start a test run and check that its terminal and grading work on the new machine.

Prompt for your agent

In the fde-gym repository at <path>, read the runner section of docs/self-hosting.md and list the network and setup requirements for an extra runner. Output a numbered checklist. Verify each item is stated in that document before adding it.

Caveat. The README says runners hold no database, storage or model key, but a runner still executes case workloads, so place it on a machine you are willing to run this code on.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page