Hi! Some of the dietary preferences can't be combined because we don't have enough recipes to support the combination (at least not yet!). We're working on batch cooking, so that should help. Currently, it takes hacks to achieve that kind of thing (like adding more family members, e.g., Daniel, Daniel Leftovers, and Daniel Leftovers 2). If you have a slow cooker, you could select that in the appliances section and then just make sure that under time constraints, you select "more than 50 minutes" for dinners. Slow cooker recipes scale up well if you do that multiple family members trick. I hope that helps!

I tried simulating this by checking Clean Eating and either checking off the pre-populated meats or searching for meats I could think of and selecting all results and plenty of recipes came up, so it seems like these two dietary restrictions should be allowed to be chosen at the same time.

Also, I checked off the pre-populated "Beef" option and a recipe came up for breakfast involving sausage and another came up for dinner involving Filet Mignon.

Thanks for the feedback! We like to make sure we have enough new recipes for many months of using the service before allowing two categories to be combined, but you're welcome to hack it that way for now. Filet mignon was a glitch (we just fixed it) but the sausage is made of pork.

What dietary preference do you have checked? Things like "dairy free" and "paleo" already omit cheese, except for those cheeses for which we have substitutes that match the overall dietary preference. If you type in "cheese", that will give you a list of every cheese used by our recipes that is not already excluded by your dietary preferences.

I've only checked 'Clean Eating.' The cheeses in the 'other' drop-down checklist are feta, fontina, goat, ricotta, and shredded parmesan.

I just tried switching from clean to 'no preference' and saw the cheeses in the 'other' list expand to the ones I expected to see. I suppose its reasonable to exclude swiss and mozzarella from 'clean' eating, but ideally for me would be a 'clean-but-not-that-clean' option that restricts refined sugars and flours, but not dairy. That may be idiosyncratic, I know.

Ah, your best bet would be a low carb plan. You'll still have dairy and whole grains in moderation but no refined sugars and flours.

Someone from the PlateJoy nutrition team emails new customers during their first week to give tips and to be available as a point of contact. There are also follow-up check-ins if people don't have specific questions right away. Some people really get into it!

Hi, this is Daniel (Christina's co-founder). You can specify appliances on the personalization page (though stovetop can't currently be unselected because it is necessary for many dinners). Lunches—with the "pack something quick" option—only use a microwave, so that can serve as a sort of work-around for people who don't have a range / hot-plate.

Complexity is handled by time preferences, which can be specified for each course (breakfast, lunch, dinner, snacks/dessert). Shorter times are less complex recipes.

Sorry, no "fewest dirty dishes" options, but great idea!

Thank you! This is Daniel (from PlateJoy). Delivery happens via Instacart. They charge between $4 and $7 per delivery, depending on area. If you sign up for PlateJoy, and you don't see the Instacart button on your shopping list, let us know and we can activate it for you. (They are constantly adding zip codes, so sometimes we don't know that a zip code is available for delivery.)

Awesome! It wasn't readily apparent that delivery is handled by a third party before signing up. I've used Instacart before, so it's cool that it's just an integration, but I wasn't sure if it was an addon I was missing somewhere that had to be added to my subscription before I checked out.

At populr.me, we use a variation on the architecture described here. One difference is that we cache resized images to S3, rather than to on-disk cache. This enables all servers to share the cache. Otherwise, when a new server is brought online, it doesn't benefit from the cache, so for a time, every request it receives incurs the most costly path of source image retrieval and resizing.

An added benefit to caching to S3 is that since S3 won't run out of space, we can cache rendered images for longer (we use S3 lifecycle to keep cache expiration simple). The scaled images tend to be smaller than the source images, so the retrieval from S3 is pretty fast. Over the past week, retrieving scaled images from S3 has cost ~46ms versus ~84ms for the larger source images.

This probably explains an error we were getting on a Node.js app running on Azure websites. Simply creating a new AWS.S3 instance was throwing this: Error: getaddrinfo ENOTFOUND at errnoException (dns.js:37:11) at Object.onanswer [as oncomplete] (dns.js:124:16)