Our image uploads seem to be not showing the lightbox expansion, so that when you click them you see a higher resolution image. This has happened after updating to .beta8 yesterday. Test image, as curious to see if the same here: [IMG_3695] Our settings (that worked ok before). [image] Any i…

[imagem] fearlessfrog: Is there something in the beta6 to beta8 that recooks all posts or something? Yep, see Discourse 2.2.0.beta8 Release Notes [imagem] Discourse 2.2.0.beta8 Release Notes Important Note: Expect high CPU usage for a few hours after this upgrade due to image re-optimizat…

It worked here, so I’ll see if our sidekiq is poorly with a /sidekiq/queues?poll=true

Is there something in the beta6 to beta8 that recooks all posts or something? We have about 3,500 enqueued Jobs:ProcessPosts being done at the moment (with only 5 busy), which would explain why it is so behind. I guess we wait?

Ah, got it - thanks! I should have looked there first. :blush: We’re a busy forum on an undersized box, so it’s taking a while to catch up.

If it helps anyone else, we’ve found that for our hardware of a dual proc DigitalOcean with 4GB seems to fall behind with a default ‘rebake old posts’ set to 80. We’ve been going for a few years and have a lot of image intensive posts, so YMMV. Our sidekiq was clear of PostProcess jobs about 12 hou…

Yeah we can probably skip queueing if more than N jobs are in the low queue

I know you guys are (rightfully) hosting tech-agnostic with Discourse, but the ideal for AWS S3 image hosted people would be moving the image processing AWS Lambda side. I’ve done that on Rails systems when it was javascript and imageMagick (moving it away from background work on the Rails side) and…

Yeah, it is an idea I have thought about in the past but we would need a custom image for this do line up all the right versions of image magick and so on. We may get there one day but odds are this is going to be in the “mega enterprise” type of setup.

In theory you can run an AWS AutoScalingGroup that runs the Discourse image, with 0 unicorns, some sidekiqs, and autoscale based in Sidekiq queue size. We almost did this for a customer, but managed another cheaper way. Running stuff with the same base image instead of a custom lambda setup (that …

[imagem] Falco: We almost did this for a customer, but managed another cheaper way. I think pretty much anything else is cheaper than AWS, but you know how the saying has evolved - ‘No-one got fired for picking IBM, Microsoft, AWS’. :slight_smile: In my use of Lambda on S3 images, we just us…

[imagem] fearlessfrog: I think what you do with Discourse needs to cover much more feature points, and I agree with you that duplicating that side to support those with, or without, AWS would be a dev pain, and probably not worth it. Yep the tradeoff is exactly this. We would be building a ne…

Lightbox de imagem parou de aparecer na atualização beta 8

Suporte ao Produto

jomaxro (Joshua Rosenfeld) 15 Janeiro , 2019 20:49 4

Yep, see Discourse 2.2.0.beta8 Release Notes

Tópico		Respostas	Vistas
User profile images loading slowly, failing to load Product Support	30	2401	23 Fevereiro , 2020
My journey into a massive posts rebake job Self-hosting	35	5091	10 Julho , 2024
Images are disappearing off of s3! Bug	56	6064	20 Setembro , 2018
"convert" process eating CPU Self-hosting	14	2643	7 Março , 2019
Rebake after CDN change missed old posts Product Support	2	596	7 Março , 2021

Lightbox de imagem parou de aparecer na atualização beta 8

Related topics