i've tried grocy a few times over and it's burned a lot of time and brain cells. is there anything that does this (or even much less than this) and just works?
i understand why it was made this complex - i code and i work with people who want everything to be so theoretically 'flexible' that nothing simple works, so i'm used to the abstraction layers. but
first try: looked at number and size of packages, no tree-shaking, code doesn't pass sniff test. dozens of megabyes for this? nope
second try: well i don't want to build this myself. i'll put it in its own instance to minimize security exposure. but hey, this release is months old and these terrible bugs have been fixed, i'll just grab newer code. missed the thing where database migrations are tested only from official releases. database breaks.
i learn sqlite syntax and reconstruct the database.
months later i download new grocy android client, which expects a v4 grocy back end. all recipes break.
i download official grocy v4 release (the third one in rapid succession, due to major bugs - luckily i hadn't tried too early).
database breaks.
i'm done. i don't care that i lose the work i already put into it. i just want to open the cupboard twice and have the same thing be there both times. help
Thanks, you're right. I've updated the docs yesterday a bit and changed some links and forgot to update them on the landing page. For anyone looking for more screenshots, they can be found in the GitHub readme.
The biggest issue with all these kind of apps is having to start from scratch, no recipes, no product info, zero, Day 1 has a very steep curve. If I just want to browse and save favorites, I'm out of luck.
I wish we could all share our recipes and product information along with their nutrition info and allergens. It would have a MASSIVE impact and a HUGE community.
All the SAAS apps are paid silos. A federated alternative could compete with them to be a similar alternative. Take Lemmy and Mastodon, for example, they have SO much content they replaced Twitter and Reddit for me.
All the Fediverse can cook. They just don't have the proper app yet.
looks great! the catch for me is that my current host doesn't have docker support. your dependencies don't look crazy so in theory i could burst it and install directly to the host environment, but at that point i'm giving myself grocy-level headaches.
reading about docker-capable hosts, i was surprised to see them starting at 1GB RAM - i couldn't run pac-man in that. what would be a reasonable expectation for kitchenowl?
One thing I did miss about grocy was the ability to track equipment in the kitchen (and house) as well, including the storage of manuals and warranty information.
Do you have any intention (or interest) in adding that?
I was pretty annoyed when my grocy install broke ages ago, and I lost all of that information but it was very useful having all of that stuff centralised.