diff --git a/README.manually-update b/README.manually-update new file mode 100644 index 0000000..9b9dc5b --- /dev/null +++ b/README.manually-update @@ -0,0 +1,62 @@ +# see also: +# +# https://meta.discourse.org/t/manually-update-discourse-and-docker-image-to-latest/23325 + + +# If you self-host Discourse, you occasionally need to run a manual update +# via the command line to get the latest security releases newest libraries. +# These updates are not picked up in admin/update, which is why you'll +# occasionally need to do this additional step. +# +# occasionally - gelegentlich + +# 1. Discourse itself should be updated about twice a month, by clicking the +# "Update to Latest Version" button in your admin dashboard (admin/update). + + +# 2 Every two months we recommend SSH'ing into your web server (using putty or +# your favorite SSH client) and doing (especially if the upgrade page doesn't +# show up or you have any issues when trying to upgrade): + +cd /var/discourse +/launcher rebuild app + + +# 3. As for Ubuntu updates, make sure you have automatic security updates +# enabled for your Ubuntu! The command is: + +dpkg-reconfigure -plow unattended-upgrades + +# However, that just covers critical security updates. Every so often +# you should get all the OS updates like so: + +apt-get update +apt-get dist-upgrade + + +# To summarize: +# ============= +# +# +# * update Discourse twice a month via web updater +# * update the container every two months +# * update the OS every six months +# + + +# Notice: +# ======= +# +# Due to the way docker packaging has changed you may also have to +# update your docker from lxc-docker or docker-engine packages. One +# way to do that is via the Docker script here (it will warn about +# an existing install but should upgrade ok): + +wget -qO- https://get.docker.com/ | sh + +# This will now use the docker-ce main versions. +# +# This is completely safe, we have never seen anything get broken by +# base Ubuntu updates. + +