Cookbook printing (requires server side rendering)

[stormbyte]

It is possible to print recipes and it is possible to put recipes in a cookbook.
But the cookbook has no print option

Add a button under /books next to edit / delete that prints all the recipes in a book

[vabene1111]

recipes are currently rendered on the front end using javascript. that means that in order to print you need to open a page. There is an option to render vue templates on the server but that has not been implemented yet thus printing of cookbooks is sadly not yet possible.

it is however planned so this feature will definitely be implemented in the future #742

[timdonovanuk]

I would say the same for meal plan would be awesome :) Thank you.

[vabene1111]

makes sense, better printing and exporting views/systems

[wechsler42]

Hi there,
I would like to second the meal plan printing feature. A nicely printed meal plan stuck to a cupboard or a fridge would be really useful. Anyway, thanks for providing us this mice piece of software.

[vabene1111]

thank you, this is definitely also planned, once server side rendering is there we can have print views for everything. Maybe we will also build some dedicated views for kiosk modes/tablets etc.

[thumm]

Besides rendering the page, another solution could be to generate a PDF via a markup file. As far as I understand it correctly, parts of the recipe description are already defined as markdown text. Using a markdown template file containing placeholders, the placeholders can be replaced with the already existing markdown text and additional recipe data. The result file can then be processed with any markdown processor able to produce pdf output.

[vabene1111]

that is correct and would likely be an easy fix but would also mean that we have to maintain a second layout with all features the normal recipe view supports, thats why we so far have held of on doing this. there is the new "expiremental" PDF exporter which can export complete cookbooks.

[Timtam]

Hello there,

I haven't found an issue for the pdf exporter specifically yet, that's why i'm asking here. I tried using the PDF exporter today using a Docker setup, but it seems like the Docker setup doesn't automatically download or contain the local chromium needed to build the PDF. Is PDF export supported via Docker, means can we somehow get the Chromium to download within the docker or is a specific Chromium docker image of tandoor already available? Thanks.

[vabene1111]

i think it should download the chromium instance on the first run which might take some time but i am not sure. The exporter is marked "experimental" and this is exactly one of the reasons for that 😂

if its not downloaded automatically i dont know how to get it into the container, maybe by manually executing into the container and running it but i am not sure.

[Timtam]

OK, so I updated to 1.0.5 and 1.0.6 from a previous release, so that means that I already got a fully working database and everything up and running, which might be the case that Chromium wasn't downloaded since it wasn't a fresh instance. Its just guesswork though, didn't check the code for that. It might however be an idea to make Chromium a default within the Docker containers (bake it in with the image), provide extra images for Docker + Chromium or allow to download it via environment variable (maybe attach it to the experimental pdf exporter variable?). There should be some way to get Chromium into Docker though at some point, when the pdf exporter isn't experimental anymore at the latest though I think.
You're right, its experimental and I am willing to give it a shot, thought i'd report it back here :).

[vabene1111]

thanks for the feedback. The exporter will stay experimental because the fundamental technology needs to change. The exporter was contributed by a member of the community because he solved a problem for himself and the solution works to a certain degree (by using chromium and a browser rendering library). This is good enought that we integrated it into the main version but i not meant to be the solution in the long term (as proper server side rendering is preferable for this).

but thank you for the feedback, i totally understand what you mean and if we were to stay with this techology it would make perfect sense