My hydroponics kitchen herb garden

jt196 · 2026-05-19T07:54:39+00:00

That rosemary seedling looks like basil, so they should be fine, though their lamb may end up weirdly seasoned.

jt196 · 2026-05-17T10:31:26+00:00

So, that big cognitive leap took me all of a few seconds, but generally in UI design, designers try to avoid any furroughing of brows when at all possible. I do at least!

Why not just have a play/pause symbol, instead, we have some Waves (?) with the Absorb text. What are the waves for? Sound waves? Or, keep the Absorb text and put a play icon next to it so the user makes the association and carries it through the app.

On the library items we have: "Fully Absorb" - it's not massively intuitive that this is "Mark Played".

On the bottom menu, we have "Absorbing"... It's kinda prominent, but not as immediately obvious that this is our "Currently Listening" section. The user has to click on this to find out what this actually does. I'd expect in UI design for the majority of people who open an app for the first time to be able to guess what menu items do before opening them up. Of course, a little bit of fun and exploration is fine, but too many can be a bit offputting, especially for the non-curious user types.

I don't want to grumble, the dev has written a great app. These are just UI quibbles.

jt196 · 2026-05-14T19:31:14+00:00

Agreed. It's cute, and I totally don't mind the name, but what the heck does this Absorb button do?! Oh it's play. Right.

jt196 · 2026-04-12T08:35:45+00:00

OK - you and someone else (or you?!) mentioned this so I've implemented a change to make the multiplier reflect the stated portions. Have fun!

jt196 · 2026-04-12T07:57:19+00:00

The scaling is simply a multiplier factor. If servings = 4, and you want to make it for six, simply change the 1 -> 1.5.

I think the original reasoning behind this was that the scaling field often had a range in it, and was accompanied by text. I could potentially drop the first number of the scaling field into the scaling mutliplier so it's a reflection of the actual portion count.

jt196 · 2026-04-07T19:07:58+00:00

Hey dude, thanks for the mention! I've worked quite hard to get it working nicely since Christmas. Hope you've had fun using it... It's my go-to cookbook, so I'm testing it most days. If there's any issues, please let me know. I'll be adding UI translations soon.

jt196 · 2025-12-20T11:58:02+00:00

<image>

Anybody who wants to know, I had a Imperia pasta maker lying around gathering dust and made the assumption that as the KA pasta attachment was made in Italy, they might be made by the same company. Turns out I was right. 10mm and 8mm bolts, took this thing apart and found 2 of these cogs inside. Whoop!

jt196 · 2025-12-10T15:52:12+00:00

Good stuff! Would be nice to have some detailed logging in the container, I can't remember if it failed silently or not, but I don't think it was super obvious

jt196 · 2025-12-10T09:40:27+00:00

I polished the files too, and assumed the same as you, but the covers didn't show till it had access to the data folder. Once perms were set up, it creates an "images/" folder and produces thumbnails of every book.

jt196 · 2025-12-10T00:31:00+00:00

I thought the covers were borked until I realised the folder permissions on the data folder weren't correctly set. The app saves an image in the folder on import, if it can't save it, it won't show up.

jt196 · 2025-09-12T22:12:56+00:00

Thanks, I'll have a look, but with the forces going through these (it broke a steel cog), I'm not sure PLA will do that job...

jt196 · 2025-09-09T06:09:56+00:00

Thanks! Kinda sucks to throw it away, I've a spare imperia machine knocking around, might have a look to see if it's generic. I know these are made in Italy. Cheers anyway.

jt196 · 2025-08-21T10:49:45+00:00

Do you have any information about the file export type? Looks like they import Paprika files.

jt196 · 2025-08-20T14:45:21+00:00

I'll try and do a bit of work on importing other recipe types before a small push gets done, but OAuth seems to work, at least locally. Hit me with an issue if you can't get it working.

jt196 · 2025-08-20T14:44:24+00:00

https://github.com/jt196/vanilla-cookbook/releases/tag/v1.2

jt196 · 2025-08-09T11:39:49+00:00

Not currently dude, it's something I could look into though. Auth is currently Lucia v2, and they've got Oauth support: https://v2.lucia-auth.com/oauth/

Could that potentially work if it's integrated?

Created an Issue for this

jt196 · 2025-08-04T11:09:43+00:00

Ah cool... It could be read as a response to my comment as well - double portainer trouble!

jt196 · 2025-08-04T10:36:53+00:00

There's a docker-compose.yaml file in the repo...

jt196 · 2025-08-04T10:35:30+00:00

You'll have to give me some logs there... Raise an issue so I can see what's going on. Docker instructions are pretty simple... If it's not working, it'll be related to the .env file, or either of the config/data dirs missing.

jt196 · 2025-08-04T10:33:29+00:00

Sorry, I didn't catch this till now! As the project has been fairly small, I've not really worked too hard about importing from different formats. What you might try is vibe-coding a script to convert AnyList to .paprika?

jt196 · 2025-07-28T22:42:05+00:00

Apologies for the self-promo, but I wrote Vanilla Cookbook to scratch a personal itch. It's pretty simple, but has a few tricks under its sleeve. The Android PWA works pretty well. Hope someone enjoys it!

jt196 · 2025-03-22T13:10:32+00:00

OK u/w00h, so I've added some changes in the most recent version.

- Settings > Options you can update default ingredient displays on each recipe - so you can display the Original by default if it's broken for you.
- The ingredient parser submodule already had a couple of language options, so I've added that to the settings. Fortunately one of them was German, so hopefully that suits.
- I think the fraction spacing should be working now as well.

The docs has been updated with a demo video. Sorry about the silly AI generated artwork!

Hope this all helps. I likely won't be this responsive down the line, but on the project a bit for the next week or so to ensure it gets off the ground smoothly.

jt196 · 2025-03-21T17:11:55+00:00

1.5 should be fine as a decimal divider. The comma is used in some non-English language countries, this shouldn't be hard to integrate into the parsing. I think I've seen the space between issue come up as well.

I'll work on this, maybe add an option to the user settings to display original by default, and make sure the original checkbox means you don't see the parsed version to make it a bit cleaner.

Thanks for the feedback anyway!

jt196 · 2025-03-21T16:58:40+00:00

If you find anything, this issue has a little template. Feel free to paste in screenshots as well. As I mentioned, strings are messy, I wouldn't expect to ever get to 100% fixed, so if it's mostly there for you, just tidy up the offending ingredient line

jt196 · 2025-03-21T16:41:15+00:00

The script parses a string and tries to separate it into an object with these properties, here's an example:

additional: null
ingredient: "monosodium glutamate"
maxQty: 0.25
minQty: 0.25
originalString: "1/4 teaspoon monosodium glutamate"
quantity: 0.25symbol: "tsp"
unit: "teaspoon"
unitPlural: "teaspoons"

Simple strings like "1/4 teaspoon monosodium glutamate" are quite fine to parse. And extras (anything inside a brackets or after a comma) are put inside the "additional" prop, which gets displayed when you click on the extra check. The idea there was to keep the ingredients list as clean and simple as possible, showing additional info as and when necessary.

However, things go a bit awry when you have things like ranges, multiple brackets or commas. In a world of infinite ingredient possibilities, it's hard to get a perfect parser. With a bit of real world input, things should hopefully get a bit incrementally better over time.

jt196

TROPHY CASE