search

reaper47 / recipya

A clean, simple and powerful recipe manager your whole family will enjoy.
https://recipes.musicavis.ca
GNU General Public License v3.0
147 stars 10 forks source link

Setting to change image compression strength. #339

Open ZeyadAmr opened 3 weeks ago

ZeyadAmr commented 3 weeks ago

Is your feature request related to a problem? Please describe. I find the image compression to be a bit too aggressive, resulting in often sub-optimal images of our beautiful recipes.

Describe the solution you'd like I'd like there to be a setting (either in the settings menu or server configuration file) to allow different compression strengths. For example no compression, minimal compression, maximum compression, etc.

Describe alternatives you've considered I tried uploading higher quality images as the source, but I don't always have super high definition images to start with.

Additional context General thank you for your work on Recipya :)

reaper47 commented 3 weeks ago

The images are now converted to WebP for better compression and quality. I wonder how this plays out for you. Please try the next Docker nightly build and let me know.

All your images in the Recipya/Images directory will be converted and thumbnails created and stored under Recipya/Images/Thumbnails the next time you start the server.

ZeyadAmr commented 3 weeks ago

The images are now converted to WebP for better compression and quality. I wonder how this plays out for you. Please try the next Docker nightly build and let me know.

All your images in the Recipya/Images directory will be converted and thumbnails created and stored under Recipya/Images/Thumbnails the next time you start the server.

I'm unable to start the docker container after pulling the latest nightly. Any idea why that might be? image

reaper47 commented 3 weeks ago

I pulled the latest Docker image and indeed get the same error. The demo doesn't user Docker thus why I haven't seen this before. I will investigate. As long as you have all your data in the volume, you should be fine. I built a fresh image using the Docker script in the deploy folder and get the error you are getting.

Edit: It has been fixed. The next build should work.