Recipe Site v1.0.0 Release Notes

Updated: 2026-09-08

Status: Final v1.0.0 release.

What v1.0.0 is

Recipe Site v1.0.0 is the first formal self-hosted product baseline for Your Kitchen Library. It is intended for households, clubs, small organizations, and individuals who want to own and operate their own recipe collection.

The release includes the application, database baseline, installer/upgrader, backup/disaster-recovery tools, administration/user documentation, and the tracked static assets needed for a clean installation.

It does not include another installation's recipe collection, accounts, secrets, backups, or other private/runtime data. Fresh installations contain only the rights-cleared example content shipped with the release.

Major v1 capabilities

Recipe and informational content management.
Category browsing and quick/advanced search.
Favorites, Want to Try, ratings, Recently Viewed, and Made It history.
My Kitchen weekly meal planning and shopping-list aggregation.
Recipe scaling, printing, email/share/export where enabled.
Import from pasted text/HTML, public URLs, document files, PDF/scans, image OCR, native Recipe Site formats, MasterCook, Paprika, Meal-Master, and Recipe Keeper-compatible workflows.
Database-backed roles and permissions with Owner/Admin management.
Owner-editable non-secret site settings.
Linux fresh installer and release-to-release upgrader.
Portable database/media disaster recovery.
Search/social metadata and XML sitemap.
Owner-only Site Health diagnostics with compact severity highlighting.

v1 database baseline

Fresh installation baseline:

33 tables
304 columns
44 foreign keys
41 tracked migrations
5 roles
19 permissions
56 grants
61 categories
0 users
0 recipes
0 tags

Fresh installs load the consolidated v1 schema baseline rather than replaying the entire historical migration chain against an empty database.

Runtime media model

Permanent content media uses the per-content path:

/assets/images/recipes/{id}-{slug}/

This applies to recipe content and informational content such as guides, tips, techniques, and references.

Temporary import media uses tokenized staging under:

/assets/images/import/{token}/

Successful saved content promotes/copies referenced media out of staging into the permanent per-content directory. The product does not use a separate /assets/images/guides/ lifecycle.

During final RC cleanup, four historical informational records created before the current promotion lifecycle were normalized out of /assets/images/import/; current references and the relevant saved guide revisions were rewritten after a verified backup and checksum validation. The unused empty /assets/images/guides/ directory was removed.

Upgrade expectations

The supported v1 upgrade path is the release-to-release upgrader documented in Installation and Upgrade.

Do not update an established installation by manually copying arbitrary files over it. The upgrader protects installation-specific state, creates/verifies recovery artifacts before changes, applies classified migrations in the intended phase, and runs health checks afterward.

The clean-target disaster-recovery restore tool is not an upgrader and deliberately refuses an arbitrary populated installation.

Disaster recovery

Portable backup/restore tools:

tools/recipe-site-backup.sh
tools/recipe-site-restore.sh

Portable DR acceptance passed on a clean GitHub-hosted Ubuntu runner in run 34265176659.

A portable backup contains database SQL, complete runtime image media, SHA-256 sidecars, and a non-secret manifest. The real .env must be protected separately.

Platform status

Linux

Linux/Docker is the fully clean-machine accepted v1 platform.

Windows Docker Desktop

PowerShell fresh-install/upgrade wrappers and Windows-specific hardening are implemented, and static Windows Server 2025 validation passed.

Real Windows 10/11 + Docker Desktop Linux-container fresh-install/upgrade acceptance is still pending. Until that passes, Windows should be described as expected-compatible rather than fully accepted.

V1 includes:

meta descriptions;
canonical recipe/guide URLs;
Open Graph metadata;
Twitter-card metadata;
Recipe JSON-LD for recipe content;
Article JSON-LD for informational content;
dynamic XML sitemap at /sitemap.php.

Site Health

Site Health is intended to remain compact and easy to scan. Normal/OK checks use normal text. Warnings use amber/yellow issue text and errors use red issue text rather than large colored cards.

Import-staging health checks follow the same tokenized staging definition as the cleanup engine. Old named permanent-media directories are not treated as staging merely because of age.

Documentation

Start with:

Licensing / project credit

Recipe Site follows the project's Value-for-Value use terms described in Use Licensing Terms. Free hosted copies retain the required small project-credit link unless the original author grants written permission to remove or materially alter it.

The software is provided as-is, without warranty. Site owners are responsible for their own content, hosting, backups, security, legal compliance, allergens, food safety, and nutrition information.

Known v1 limitations

Real Windows Docker Desktop acceptance is pending.
Instructional inline images do not yet have a first-class stored alt-text field.
Optional starter/sample content is not part of the clean baseline and should remain opt-in/rights-cleared.

Final release validation

The isolated clean-machine integration diagnostic passed in run 34297855128, including install/health, exact pristine baseline counts, DB-backed Advanced Search/Made It tests, SEO/search smoke, backup/checksums, upgrade dry-run, and final health.

Step 10 also produced and merged browser-fidelity and Reference regression fixes (PRs #351 and #354), followed by the V2 parser title/nutrition recovery fix in PR #358.

The fresh exact-RC Step 10 clean-machine gate passed in run 34305745071. It covered PHP lint, maintained parser/import/export regressions, security/UI hardening, My Kitchen planning, release-package checks, a fresh Docker install with exact v1 baseline counts, DB-backed Advanced Search and Made It checks, search/SEO smoke, backup/checksum verification, upgrade dry-run, and final product health.

That exact RC commit was then fast-forwarded to production by guarded runner-health run 34305930303, preserving the protected local www/includes/config.php. Read-only live verification passed in run 34305975117, covering exact deployed SHA, product health, core pages, Advanced Search, sitemap output, guide metadata/canonical/Article JSON-LD, and protected checkout state.

All documentation Ask a question