this post was submitted on 19 Jun 2023
7 points (100.0% liked)
Café
777 readers
3 users here now
Welcome to our virtual third place, The Café.
Come on in and make a new human connection over a cup of coffee (or Teh Tarik). This is a casual community, do whatever you want, share your oyen pics, your frustrations, and even organize a weekend picnic with the community. The world is your oyster.
Rules are simple, be kind and civil with each other. As with any other café, rude patrons will be kicked out.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
We can open a GitHub issue on their repository too, but I'm not sure which part is causing the issue(the UI or the image storing) as I'm not home rn. I'd figure it would be better if I can at least figure out where the issue came from before reporting it
dont know if this is of any help, but from the docs I read, it seems lemmy is using pict-rs for image hosting, and pict-rs uses imagemagick.
since you mentioned the Ansible script, I took a look at its repo, and perhaps dcx may also want to watch out for this issue: https://github.com/LemmyNet/lemmy-ansible/issues/87
Oh no, not the log files nightmare :( this shit was haunting even my company lol because we started adding new tools But that part can be modified in the deployment script I think... I'll take a look at the deployment scripts later.
Thanks, I'll take a look at imagemagick too. I saw pict-rs yesterday but I haven't looked up what's that