ockham
commented
11 years ago Submitted by SourceForge user nobody on 2009-05-04 20:33:25 UTC.
Go for it :)
Seriously, I've long considered something like this. It would be nice to pool all the recipes that people have entered... there are, of course, problems, including scaling the server side (who's going to pay for the server side exactly?) and licensing (many of the recipes in my DB are typed directly from magazines or books).
That's one reason I've worked so hard to make Gourmet's web import work well -- it makes it very easy to use the resources you already like (epicurious, foodnetwork, what have you), and import recipes from there.
Converted from SourceForge issue 2786593, submitted by SourceForge user bolsh on 2009-05-04 13:27:41 UTC.
Gourmet would be so much better if I could search online for recipes and upload my own, to create a shared database.
Imagine starting up Gourmet for the first time, and I type "Bourguignon" in the search box, and I see 8 different recipes for boeuf bourguignon, with ingredients & instructions, with the author name & upload date & rating. I could download the recipe locally, rate it, perhaps even propose alternate instructions & upload?
I don't think it would be too difficult to throw together a database & RoR application to provide the required RESTful interface, you could even keep a local index of the database to allow offline searches, and allow online browsing too.