Are you storing the recipes in Git repos or in the Postgres DB?
If in Postgres, what is the format? Do you put each receipe in a single JSON field? If not, what does the data structure look like?
111–120 of 159 posts
Are you storing the recipes in Git repos or in the Postgres DB?
If in Postgres, what is the format? Do you put each receipe in a single JSON field? If not, what does the data structure look like?
I should be able to go to a user and their recipes with the same ease as on github. Having unique IDs for recipes exposed in the URL isn't really necessary.
How are you doing volume to weight conversions? Do you have a big table of weights-by-volume for different ingredients?
Yeah, densities and fuzzy matching. It'll get more intelligent eventually, but does a pretty good job on common ingredients at the moment.
E.g. I'm seeing 1 cup of steamed rice - being British I have no idea what that means. I turn metric on and it tells me 237 milliliters of rice, whereas I would be expecting grams. I'm pretty sure measuring solids by volume is a US-only thing.
The idea for this has been around for a for a while. http://forkthecookbook.com/ goes back to 2012. And its an interesting idea. Recipes can't be copyrighted and and recipes are generally derivative. The data is generally well structured, and fairly standardized (ingredients, equipment, instructions, photo, with optional fields for prep & cook time, servings, notes, difficulty, etc). But there are two primary issues:…
hello, FtC author here... it's mainly a zombie project now (you know, dead, but still has active users)
Is this project open source or does it plan to be at some point? I've looked at some of the other projects out there that are similar, but many seem to die based on the founder running out of steam or getting busy with other stuff. I would really be interested in contributing to this or a a similar project if anyone has a suggestion for one that is open.
I'm a huge fan of the fact this does weight conversions (cooking by weight is now my favourite, and I've been looking for a site that is just weights, so this looks like a win to me :-) ). One note I'd make, though, is that US, UK and Australian cups are all different sizes. (and possibly others?) And from the one recipe I saw it looks like you're using UK cups? But, possibly not as well... Either way, it might be wo…
> Somewhat related, some sites call out egg weights too, and that might be something to try and do here too? Some technical recipe books I've used just specify the weight of total egg. Not that useful for a home cook though. For that matter, I'm curious what egg size descriptions is like in other countries; in Australian shops they're like condom sizes - I haven't seen 'small' or 'medium' eggs for over a decade.
This looks promising and fairly well done, but it's lacking a few critical features IMO. The first obvious one is a way to Diff a recipe and it's Forks (unless I missed that). The harder and maybe more important one, is an issue that GitHub itself still hasn't figured out how to solve either. There should be a process for a fork of a recipe being able to explain why it is better than the original, and have the fork b…
Have you thought about simplifying the UI by changing "Forks" to something like "Twists" or Takes (as in 'my twist on' or 'my take on').
We all understand what I fork is but the average user will likely get confused, and not just because a fork is a kitchen utensil!
I'm not sure how you would go about adding this though, its quite different from the structure you have already