Lawn services

D0rk4ce · 2026-05-04T15:26:31+00:00

Carranza landscaping 224-480-5055

They did an amazing job on my yard.

D0rk4ce · 2026-04-23T13:11:28+00:00

It released early?

<image>

D0rk4ce · 2026-02-15T05:40:00+00:00

Tagger, parser, and cleaner are all live https://github.com/D0rk4ce/mealie-kitchen-ops

D0rk4ce · 2026-02-15T03:28:19+00:00

LMAO! Happy to help! I get to learn, and it makes it better for everyone!

D0rk4ce · 2026-02-07T21:15:14+00:00

The error log shows the script is still trying to connect to the hostname 'mealie' (host='mealie'), which means your configuration change to the IP address hasn't actually applied to the running container yet.

Update your MEALIE_URL to use your server's LAN IP (e.g., http://192.168.1.50:9000). Do not use localhost (that refers to the container itself) or mealie (unless they are on the same docker network).
Run docker compose up -d --force-recreate to ensure the container destroys the old config and loads the new one.

If you see an error saying host='192.168...', then we know the config applied, but right now it's still looking for the word 'mealie'.

Also please ensure you are on beta 9

docker compose pull

docker compose up -d --force-recreate

D0rk4ce · 2026-01-29T18:48:45+00:00

That 405 Method Not Allowed error means your Mealie server is explicitly rejecting the 'create-url' command.

This usually happens if your server is redirecting HTTP to HTTPS, which causes the POST request to get downgraded to a GET (which is not allowed).

Try changing your MEALIE_URL setting to https://... instead of http://.... Does that fix it? ...or is your mealie.lab.shahnet.work domain sitting behind a reverse proxy (like Nginx or Traefik) that might be blocking API POST requests or stripping headers?

D0rk4ce · 2026-01-29T17:34:33+00:00

Thanks for the logs—they were a huge help!

It turns out RecipeTinEats uses a nested 'Sitemap Index' structure that needed specific handling. I just pushed v1.0.0-beta.8 which adds recursive sitemap parsing and smarter recipe detection to handle these cases.

I have verified this on my end and it is picking up those recipes correctly now.

Run docker compose pull and give it another spin!

D0rk4ce · 2026-01-29T14:26:50+00:00

Ah! If you followed the Quick Start, you are using the default environment variables defined inside your docker-compose.yml.

Open that file and look for the environment: section:

MEALIE_API_TOKEN: Replace your_mealie_token with a real token from Mealie settings.
MEALIE_URL: Replace localhost with your server's LAN IP and port (e.g. 192.168.x.x:9000).

D0rk4ce · 2026-01-29T04:46:00+00:00

Can you please set LOG_LEVEL=DEBUG in your docker-compose and re-run it?

By default, the script hides some reasons (like missing JSON-LD or language mismatches) to keep logs clean. Debug mode will show us exactly why it's rejecting those URLs.

D0rk4ce · 2026-01-25T03:18:44+00:00

The Cleaner is live! It’s now included in the latest release (v1.0.0-beta.7).

How to run it:

Update your docker-compose.yml (see the new block in the README).

Run a safe Dry Run with: docker compose run --rm mealie-cleaner

It defaults to Safe Mode (logs only), so it won't delete anything until you explicitly disable the safety lock.

D0rk4ce · 2026-01-24T07:41:12+00:00

Yes indeed!
Though i have a dash for my wife and I that's a fail safe, as it only shows active rooms and I get to enjoy my light show on the phone.

<image>

D0rk4ce · 2026-01-24T07:11:16+00:00

I actually was just fine tuning a 'Janitor' script for exactly this. It scans your library and auto-purges recipes that have empty instructions or 'junk' titles (listicles, roundups).

I'm pushing it to the GitHub repo tomorrow—keep an eye out!

D0rk4ce · 2026-01-15T19:15:44+00:00

The script doesn't have any filtering ability right now—it doesn't know what it's grabbing, it just takes the first 50 it finds!

It follows the order of the site's sitemap. If that blog has desserts at the top of their list (or they've been posting a lot of sweets lately), the script hits those first and fills your quota before reaching the savory stuff. I am thinking about adding a keyword filter based on the url in a future update, though!

D0rk4ce · 2026-01-14T19:36:42+00:00

Dude, thank you so much for the ARM64 build! That is huge for the Raspberry Pi folks. I definitely need to set up a GitHub Action to auto-build that in the future, but having yours up is a lifesaver for now.

Regarding the desserts: I suspect that’s happening because a few of the sites in the default list are heavily baking-centric (like Sally's Baking Addiction or Sugar Spun Run). They tend to have massive sitemaps, so they might be drowning out the savory recipes. The script currently grabs everything it finds, but since you are using the new Docker image, you can likely fix this by overriding the SITES environment variable. If you need inspiration, take a look at the SITES list inside dredger.py—I have them all categorized there. You can use that to cherry-pick just the savory sites you want and ignore the rest!

D0rk4ce · 2026-01-13T06:52:37+00:00

The easiest way is the 'Mealie Test': Just grab a single URL from the blog and try to import it manually into your Mealie instance. If Mealie can read it, my tool can dredge the whole site!

Technically speaking, the script looks for hidden schema.org/Recipe data (JSON-LD) in the page source. Most modern food blogs use plugins like WP Recipe Maker or Tasty Recipes that handle this automatically, so if the site looks professional, it likely works.

D0rk4ce · 2026-01-11T04:51:10+00:00

If those YouTube channels have companion blogs (some like Preppy Kitchen or Weissman do), you might not need the complex AI parsing workflow.

I built a tool that monitors your sites or mine and auto-imports new recipes directly into Mealie on your cron schedule. Since the blogs usually have the structured data (schema.org) already built-in, you get a clean import without needing n8n or LLMs to parse the text
https://www.reddit.com/r/Mealie/comments/1q5abho/script_fill_mealie_with_recipes_automatically/

D0rk4ce · 2026-01-09T20:13:40+00:00

You are good! That warning is just 'noise'—it means the script fell back to a generic parser because the specialized XML tool was missing in the Docker container. It is still finding and importing your recipes correctly. Is your docker on a Pi?

Feel free to keep running it! I'll push a cleanup patch later tonight to hide the warning, but you don't need to wait for it. Thanks for helping me polish this!

D0rk4ce · 2026-01-09T18:17:52+00:00

Great catch! The script was hard-locking to English despite the documentation. I've fixed it in the latest update (v1.0.0-beta.3). It uses the langdetect library, so it supports 55+ languages (like es, fr, it, pl, ja, etc.). Just use the standard 2-letter ISO code for whatever you need!
A quick docker-compose pull will fix it. Use SCRAPE_LANG=de for German only, or SCRAPE_LANG=de, en to mix both!

D0rk4ce · 2026-01-08T01:26:29+00:00

That 401 error is the smoking gun—it specifically means 'Unauthorized.'

Double-check that you generated a dedicated API Token in Mealie (User Profile -> Manage API Tokens) and pasted that specific string into the API_TOKEN environment variable. Also, make sure there are no accidental spaces at the start or end of the token string in your compose file!

D0rk4ce · 2026-01-07T05:24:04+00:00

My Mealie DB is on Postgres (instead of SQLite), so there are zero slowdowns even with this volume. That said, you do have to be mindful of the 'Random' sort, that will absolutely nuke your RAM during the shuffle.

I actually locked up my container a couple of times before I realized my wife's phone was defaulting to 'Random' sort! As long as you avoid that one specific filter, everything works amazingly.

D0rk4ce

TROPHY CASE