Recently, I’ve been migrating a bunch of data from an old forum (Google Spaces, actually) to my own Discourse instance. As part of this process, I uploaded a bunch of images through the Discourse API with the intent to reference them later from subsequent posts. I thought I had 30 days to do this, but it turns out that the default for moving things into the tombstone directory is just 2 days, and then they are gone entirely in 30 days. My mistake.
Now, all these images are uploaded to an S3 instance, as I do with all uploaded content. So (because it was late at night and I wasn’t thinking all that straight) I simply went into S3 and moved all the stuff out of the tombstone directory into the normal images directory, and made the content publicly accessible (as the “normal” uploads are). I was then able to refer to them from the posts as intended. After I did this, it occurred to me that perhaps this was not the greatest idea I have ever had.
So my question is:
What horrible thing have I done to Discourse’s internal bookkeeping by manually moving this stuff? Is there some image database that I’ve broken? Is there a task I can run to rebuild it? I’d turned off garbage collection (temporarily, I hope) at that point, and I want to reenable it, but I don’t want Discourse to re-tombstone these images. Any advice would be greatly appreciated.