It all started when I noticed that upgrading failed on docker_manager and discourse itself, but would magically be updated the next time I checked. The updating would pause at “purging temp files” and I would leave it for an hour or two, but when I come back it would say failed at “killed” or just at “purging temp files” and then it would be magically updated. I’ve assumed it has actually updated successfully even with the weird behavior.
Today while upgrading to 1.7 it has done the same thing. This time I decided to look through the settings and found, which I assume are new setting categories, this:
I decided to boot up the command line to the server (Digital Ocean) and remove any plugins, just in case. However, after following discourse/INSTALL-cloud.md at master · discourse/discourse · GitHub for the installation, I noticed
/var/discourse did not exist and it now resides in
/var/www/discourse. This could be Digital Ocean moving it around, or how the Discourse installation ends up, but I’m not sure. Anyways, inside
/var/www/discourse I attempted to use
./launcher which does not exist. What’s happened?