Yeah… we followed this guide to set up the nginx reverse proxy, but this was for a standalone setup and did not mention the uploads because it was not needed to be transferred in standalone mode:
And we followed this guide for two containers, which also did not mention doing any DB restore or transferring any upload directory:
I think we can easily understand things. Here is the clue you were missing to help explain, for reference:
The main tutorials on this configuration leave out the fact that you should either do a DB restore, or transfer your uploads manually to the new container because we did not include that.
Or course, it makes sense now after figuring this out 100% on our own (again!) because it is not in the tutorials. LOL
Everything is easy after you know what the problem is.
PS: In closing. Thanks to everyone who wrote various tutorials. They were a big help! Much appreciated. On our end, this configuration is done and we will no longer use any standalone configuration on any discourse sites in the future. Our normal "default’ will be two containers with a reverse proxy to a unix socket. This works the best for making updates and switching containers in real time with almost zero down time. Good stuff!!
Discourse is GREAT!!
Well done Jeff @codinghorror and Sam @sam ! BRAVO!
This is fairly easy to get working, but as I mentioned earlier, we don’t use S3 and other cloud storages services; and prefer to keep things “simple” and so our backups are just rsyned to offsite storage. We prefer it this way… it’s one less thing to debug and we can “live” without S3,