The discussion is about configuring the Discourse s3 backup folder. cmdntd is experiencing an issue where Discourse saves backups to the default folder, making the default download link unusable. To access the backup, the link needs to be manually edited to include the default folder. cmdntd is looking for a way to limit the backup settings area to avoid overwriting other matching characters in the database. Lilly suggests that something might not be set up properly and asks if this has always been the case or if a change was made. cmdntd is trying to set up backups with seaweedfs s3, but is having trouble finding the necessary configuration settings. A potential solution involves modifying the backup link using a rails command, but cmdntd is concerned about the safety of this approach.
When uploading to s3, discourse will save backups to the default folder
this makes the default download link of discourse here unusable: https://domain.com/admin/backups/backup.tar.gz?token=id
must manually edit the above link as follows to use: https://domain.com/admin/backups/default/backup.tar.gz?token=id