Replies: 22 comments 36 replies
-
Yeah I;m loving this. It's relazying.
|
Beta Was this translation helpful? Give feedback.
-
I've been out of the loop for a few months while waiting for the 5.0 update that was going to include printing and I see it's not only here; but there's already been two updates to it! I checked out the print function and it's great. Until I can project my recipes onto a cabinet door, I like using a print out copy of recipes. This way I can make notes if it's a new recipe and I'm not getting my tablet or phone splattered. You should see some of my recipes. They've been used a lot and it shows! I saw a thread on Discord about your plans on different print options. You mentioned about wanting it to scale like the King Arthur Page. I looked at the link and that's exactly what I hope to be able to do with Mealie, too. If I took the time to include notes and nutrition information in my recipe, I'm hoping I'd be able include those in the printout along with it's picture. I'm a visual person. I have a hard time visualizing a recipe without a picture attached. That's why recipe books include pictures. Thank you for all the hard work you and everyone who's contributed to making Mealie what it is today. It is really coming along and a great place to store cherished recipes. Really looking forward to the different print functions to get implemented. |
Beta Was this translation helpful? Give feedback.
-
As requested, dropping my 2 cents from feature requests here about TOTP 2FA when authentication is reworked. Enjoying using the product and looking forward to contributing when I can. |
Beta Was this translation helpful? Give feedback.
-
Update 8/25I'm going to start posting periodic updates on the progress over in
|
Beta Was this translation helpful? Give feedback.
-
Saw another post in the feature request discussion where you mentioned to put ideas here for authentication. Would be cool to see SSO integration to do single sign on with authentication applications like Authelia, Google Auth, etc. using something like OpenID Connect. I love this program and have been using it in my homelab to share recipes with the whole family. Thank you for great work and time you have put into this! Maybe one day ill be able to contribute more! |
Beta Was this translation helpful? Give feedback.
-
Thanks for your work! Great piece of software! |
Beta Was this translation helpful? Give feedback.
-
New v1.0.0 docs are up at https://nightly.mealie.io/changelog/v1.0.0/ Largely they're the same, but I'll be updating them as I work through v1. Check the change-log for new features and improvements |
Beta Was this translation helpful? Give feedback.
-
Are there plans to integrate SSO with SAML or OpenID such as Authentik, Keycloak or Authelia? |
Beta Was this translation helpful? Give feedback.
-
The latest v1.0.0 demo now has an NLP model-driven ingredient parser https://beta.mealie.io/admin/parser Huge step in making recipe scaling super easy. |
Beta Was this translation helpful? Give feedback.
-
Just wanted to throw this out there real quick... AND saw your beta demo and immediately loved the rewrite! Keep up the great work! |
Beta Was this translation helpful? Give feedback.
-
Just finished up work for the new meal-planner. |
Beta Was this translation helpful? Give feedback.
-
What is the reason v1.0.0 is split in two? (mealie-frontend and mealie-api). Are both docker files required? |
Beta Was this translation helpful? Give feedback.
-
I apologize in advance if it's dumb question and not specific to 1.0 (though as I understand food parser is a new 1.0 feature) cause I've just installed mealie for the first time and decided to start with 1.0 right away cause I need the shopping list feature. Why do all built-in ingredients have dashes instead of white spaces? And if there's a real reason behind that then why isn't the parser adjusted to recognize that? Basically what it means right now is that I either have to manually select the existing "dashed" ingredients or create duplicates without dashes: Also would be great if the parser understood that cherry tomato and cherry tomatoes is the same thing cause otherwise I'd have to have even more versions of the same ingredient. |
Beta Was this translation helpful? Give feedback.
-
This is a bug, the ingredients should be created without bugs. can you file an issues for this?
I believe the parser should depluralize the ingredient before it get's processed. I'm using a pre-trained machine learning model to parse the ingredients, so unfortunately there's not much I can do outside of pre-process the strings. It should be understood that it's not silver bullet to automatically handle all cases, it's just there to help you with some of the easy cases - which will work much better when the bug you described is fixed. Thanks! |
Beta Was this translation helpful? Give feedback.
-
Are there instructions somewhere for how to install the v1.0 beta? I see the frontend-nightly and api-nightly tags on dockerhub but I'm not 100% sure how to use them. |
Beta Was this translation helpful? Give feedback.
-
What version of hhursev/recipe-scraper is currently being used in V1 (and how do I check)? How often is it updated? |
Beta Was this translation helpful? Give feedback.
-
I wanted to ask about the frontend and backend environment variables for the current nightly build. When I got to both links (https://nightly.mealie.io/mealie/documentation/getting-started/installation/frontend-config/ and https://nightly.mealie.io/mealie/documentation/getting-started/installation/backend-config/) I am seeing a 404 error. Is there anywhere else I can see these variables? Is this a known issue right now? Thanks |
Beta Was this translation helpful? Give feedback.
-
Two questions regarding servings: Apart from that, its a really cool project. Thank you for your effort! |
Beta Was this translation helpful? Give feedback.
-
@hay-kot thank you so much for all the work you've put in. I wonder what was your main reason for making the decission to make the site login only, and essentially not have a public recipe book and/or a shared recipes section where people cand all put their recipes together? At one point, in issue #597 you even said that you won't be implementing this, so I'm curious why the change of heart. I've been waiting for v1 for some awesome features that you've implemented, but it now breaks the use case I wanted to use this for unfortunately. My apologies if this was discussed somewhere else, but I couldn't find it with the keywords I used to search. |
Beta Was this translation helpful? Give feedback.
-
Not only would this be awesome for food but also for brewing or distilling recipes. I tried to scrape this url but it didn't work. https://www.homebrewersassociation.org/homebrew-recipe/rushmore-ipa-extract/ |
Beta Was this translation helpful? Give feedback.
-
I have to say, I find the Meal Planner in the latest version much less intuitive than the 0.5.x versions. I have made a rule for a meal plan, but it only populated three days. When I try to add a random dinner, it says I have no recipes that match my rules, despite having recipes in the categories that I've selected for dinners. Seems when I press the 'Random Dinner' button, I get a 404 error after the POST request. Related to the XHR. |
Beta Was this translation helpful? Give feedback.
-
First of all thanks for all the hard work! Mealie works intuitive and fast. I really don't have that much features I find missing. For me, most important is stability. If I commit to using Mealie instead of my trusted stack of printed out recipes, than it must be stable. Migrating from 0.5 tot stable-3 scared me a bit. So (commitment to) backwards compatibility for recipes, categories and labels is high on my list. |
Beta Was this translation helpful? Give feedback.
-
Hey all it's been so cool to see how much everyone is enjoying using this thing I've put so much time into. Given where I was at in my programming knowledge when I started the project, I made a lot of poor design choices and wrote a lot of Javascript that isn't scalable. I've taken some time to assess the project and have determined that I really need to take a step back and re-look at how the Frontend is put together. Effectively I'm looking at a fullish rewrite of the Frontend. I've already started the process and am already seeing how the project will improve.
Here's what to expect for the next few months on the stable branch
The new version will be targeting v1.0 which means we're shooting for stability and a non-breaking API moving forward from their. No more backup/restoration process 🎉. We'll be moving to a 2 container setup with a Backend and a Frontend container with server side render which means faster loads speeds and more customizable sites. As of right now I already have a few really cool features working...
More info will come soon, but in the mean-time feel free to provide feedback, leave kind words, or yell at me in the comments below.
I'm confident the changes I'm making will be all for the better 👍
P.S. if you're interested in helping out in the rewrite join the discord and get in touch. We're working with TypeScript and Nuxt.
Beta Was this translation helpful? Give feedback.
All reactions