I’m migrating a self-installed discourse to a docker install.
As my database is setup with amazon RDS, I found no complication in just setting up the docker version and pointing to the old-good database we were already using. However, as expected, all my assets like attachments and and profile pics are in the
/public folder of the old installation.
My expectations were that I’d easily find a
/public folder in the docker version and make a
cp -r of my files there, but docker seems to create a slightly more complicated directory hierarchy with some hashes and stuff. eg:
and I now have a few
/public folders with different hashes each.
I’ve found this post: Migrating an old Discourse install to Docker so far.
But checking what will be done by this, it looks like it’s gonna dump the whole database and some other stuff as well (which seems to me to be an overkill, as I’m using the same db and we have a rather big one running in production).
Does anyone know or can think of a nice way of doing this?
Or maybe a workaround for my
cp -r plan