Hello, Anyone can help me? I, [2025-02-24T17:35:41.516926 #1] INFO -- : Terminating async processes I, [2025-02-24T17:35:41.516987 #1] INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/15/bin/…

I’m just wondering, why not add an option to keep the assets on the Discourse core server (I mean, without storing them on S3)? As long as it doesn’t affect uploads or the process of clearing orphaned files, it seems like a viable solution.

[תמונה] Jay Pfaffman: Is that rake task the only way that expired assets get removed? Yes. It is not like this is a big deal. Normal sites updating every once in a while won’t see much difference. People can setup their own lifecycle rules if they care about this stuff. [תמונה] Jay Pfaff…

FWIW, it looks like Digital Ocean has no trouble deleting backups nor expiring missing assets. For providers that are broken, it’d take a long time before unneeded assets caused much of a problem. Keeping a whole bunch of backups including a huge database and all uploads, could be quite a problem …

Hi - I’m Pat Patterson, Chief Technical Evangelist at Backblaze; I arrived on this thread because I have a self-hosted proof-of-concept Discourse forum, and I happened to bump into this exact issue today while configuring my forum to use Backblaze B2 for backups and uploads. Setting AWS_REQUEST_CHE…

[תמונה] metadaddy: I’m Pat Patterson, Chief Technical Evangelist at Backblaze thanks for posting!

[תמונה] metadaddy: but it’s helpful to know that it doesn’t cover a number of scenarios, including: Deleting files - Discourse is using the DeleteObjects S3 operation to delete multiple files in a single API call, as it should. Yeah, and AWS SDK maintainers are only giving us the cold shoul…

I’m glad to see that the B2 team has also noticed this issue. Here’s my temporary solution: I commented out all the configurations related to S3 in app.yml and successfully rebuilt Discourse. This does not affect access to previously uploaded files on my site, and any attachments uploaded during t…

[תמונה] Yt.w: btw, I still wondering, why not add an option to keep the assets on the Discourse core server (I mean, without storing them on S3? ??? That is how Discourse works out of the box, you need to opt-in explicitly with shipping assets to an object storage service.

I mean, it might be good to have an option to keep Discourse core assets (JS, CSS, etc.) on the local server. At the same time, only user-uploaded files would be stored in S3

You can do that by not enabling “use_s3”, but they are small, I’d just push them and not worry about the wasted space.

לא ניתן לשחזור בשל עדכון של gem ה-AWS SDK והגנות חדשות של שלמות נתוני AWS

תמיכה התקנה

Falco (Falco) 26 בפברואר,‏ 2025,‏ 3:27am 30

Yeah, and AWS SDK maintainers are only giving us the cold shoulder on this

https://github.com/aws/aws-sdk-js-v3/issues/6819#issuecomment-2625426822

נושא		תגובות	צפיות
Error Upgrading from 3.4.0.beta4-dev to 3.5.0.beta1 Support	2	183	6 במרץ,‏ 2025
Configure an S3 compatible object storage provider for uploads Self-Hosting cdn , configuring , how-to , reference	265	49767	2 ביולי,‏ 2026
Rake uploads:migrate_to_s3 error Self-hosting s3	8	888	6 בינואר,‏ 2020
Cannot upload or backup to Amazon S3 Self-hosting backups , s3	3	2185	14 באוקטובר,‏ 2015
Issues with AWS CDN and S3 Self-hosting cdn , s3	22	685	30 בדצמבר,‏ 2025

לא ניתן לשחזור בשל עדכון של gem ה-AWS SDK והגנות חדשות של שלמות נתוני AWS

נושאים קשורים