2.7.0.beta2 upgrade mislukt

This long story has a big happy-end and could be categorized as a storm in a teacup. I learned a lot about Discourse and as a consequence plan to stay around indefinitely. Here is the itemized happy-end description:

  1. My problem upgrading from Beta1 to Beta2 was manifested by the PuTTY console timing out. I interpreted this as a colossal crash in the Discourse upgrade task and spent a lot of time learning Discourse “internals” - a rabbit hole I am very happy to follow needlessly

  2. The solution to my problem is extremely simple (once you know where to “push”) - simple as 1, 2, 3 below


    (the fact that I started with too big “keep-alive” interval, let me to believe how PuTTY is really a crappy software and spent a lot of time switching from SSH based droplet access to [id, password] based authentication needed for Digital Ocean’s own console (which is really bad). Note that this experiment completely rehabilitates the PuTTY tool.

  3. @Falco opened our “collective eyes” pointing out to simply use Windows 10’s built -in OpenSSH (thanks to Scott Hanselman).


Since I already promised to @codinghorror to write the best ever document presenting Discourse to the world as a thank you for his (and his team) help to get me understanding Discourse, @pfaffman let me make this @Falco 's suggestion be the first part of my document