Fork Recipes
Fork Recipes is a Dockerized Python web frontend for ForkApi that lets home cooks create, organize, save, and print personal food recipe collections.
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
42/100 Fair
- Maintained
- 65last commit 100 days ago
- Popular
- 3771 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- No data
- Security check
- 201 serious finding, 9 minor, CI, tests
Based on 4 of 5 factors.
Security check: 1 serious finding
- Uses certifi 2024.8.30, which has a known critical vulnerability (PyPI)
Automated checks on commit 1e3018a, 21 Nov 2026. Not an audit.
Availability: platform listings confirmed today
- GitHub stars
- 71
- Open issues
- 1
- Last commit
- 2026-08-13
- Latest release
- v.4.1.1-Hot-fix
- License
- BSD-3-Clause
- Activity
- stale
Checked yesterday - source: GitHub (mikebgrep/fork.recipes)
Resources & Compatibility
Requirements not published yet.
Checked yesterday - source: Docker Hub image tags and published docs
First-install notes
- Installation Install the Docker-deployed web application independently of the ForkApi installation instructions; use owned SSL certificates or a non-SSL domain. source
- Deployment requirements Deploy the Dockerized fork.recipes app with a Postgres database and a ForkApi instance; SSL and no-SSL configurations are available by default. source
Fetched yesterday - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Do I need to install the web frontend using the ForkAPI setup guide?
No, the frontend client installation is independent from the ForkAPI installation. You still need to set SERVICE_BASE_URL in the .env to the ForkAPI endpoint with the required protocol.
Can I deploy it without SSL on the app itself?
Yes, a no-SSL configuration is available. It is useful for local use or when another service or host handles SSL by default.
What database options can I configure in the .env file?
DEPLOYMENT_TYPE can be postgres, postgres-ssl, sqlite, or sqlite-ssl. If using Postgres, DATABASE_URL must be set to a Postgres connection string.
What do I need to change when installing on a Raspberry Pi?
Change the backend service Docker image in the docker-compose file to mikebgrep/forkapi:arm64.
Which features require OpenAI?
Recipe scraping, ingredient-based recipe generation, translation, audio narration, and emoji handling during scraping require an OpenAI token. Audio narration is listed as English only.
Can I back up or restore the recipe database?
Yes, the app includes backup snapshot import, export, and apply for database backup snapshots.
Answers sourced from github.com, mikebgrep.github.io
Community
Collected yesterday - public community threads