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

How to run a private FDE Gym site for your team's engineers with Fde Gym

Host the judge for your own people, with an admin console for cases and members.

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

Credentials. Admin accounts control members, runs and the model spending cap, so choose the first sign-up with care and protect the admin password.

Who it is forA engineering lead or training owner at a company who wants new delivery engineers to practise customer work on cases the team controls.

The problemPublic practice sites do not show your own delivery patterns, and you need control over who signs up and which cases are visible.

The outcomeA team-run FDE Gym instance with an admin account, uploaded cases, and a leaderboard and submissions view for your members.

What you need first

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

Steps

  1. git clone https://github.com/deeplethe/fde-gym.git && cd fde-gym
  2. docker compose up --build
  3. Sign up first on the site so your account becomes the admin, then open the admin console.
  4. Upload or file a case in the admin console, and pause or remove any case that is not ready.
  5. Read docs/self-hosting.md for settings, managed database and object store options, and the Security section before you invite anyone.

Prompt for your agent

In the fde-gym repository at <path>, read docs/self-hosting.md and list the settings a team needs to change before sharing the site. Output the list as bullet points with the setting name and what it controls. Verify each item appears in that document before listing it.

Caveat. The README says the site executes the code people write, so a shared deployment needs the isolation steps in docs/self-hosting.md.

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