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
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
I haven’t read much of the source code(need some time to figure things out), but I hope I’ll find something eventually 🥹
Ohh man, thanks for the work!
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