On Discourse version 1.6.1 we have customised as per our requirement and added multiple models both on rails and javascript side and some customisations in Javascript libraries as well.
Now we are trying to integrate Babble chat plugin for which we are facing many issues like manually placing the missing JS files and updating relative path of libraries imported. So we are planning to upgrade the discourse version to latest with which we can easily integrate babble chat plugin. Below mentioned points are my concern.
- Easy way to integrate babble chat plugin with discourse 1.6.1. - Upgrade discourse with out effecting the existing functionality(created by us).
I really hope you modified Discourse in some way other than modifying the Docker container directly. Assuming you have these modifications stored in source control, pull and merge is your best route. If you didn’t you’re going to be in a rough time trying to find your modifications, transfer them, and test them.
No, there is no command, you performed your customization in an unsupportable way. You are going to need a very skilled developer with lots of time to get you upgraded to latest, something I strongly recommend doing cause there are may public security vulnerabilities that have since been patched.
Wanted to chime in here with a personal anecdote: A few months ago I took over managing a Discourse forum where I work. The forum is used seasonally, for about 5 months, then not touched for 7. When I took over we were having all sorts of intermittent issues. After the forum went “partially down” 3 times in 4 days, it was decided that I’d work with our IT staff to figure out what was wrong. Almost 6 hours later, we found that a former dev modified Discourse files, set them to overwrite the existing Discoures files each update, and this was the cause of our issues. 4 days of nearly full-time work later, we’d managed to stop the files from being overwritten, develop a plugin, and get everything working again.
Why am I sharing this? I just want to emphasize that modifying Discourse is unsupported (read: not a plugin) ways is bad. While we only had a few files modified, it caused us major issues that fortunately were caught before our forums went live again for the season. Please take the time to un-modify your install, put the changes into a plugin, and only then attempt an update.
Yes, it is generally safe to upgrade multiple major releases at once. Rails migrations handle that for you.
However, it is always a good idea to take a full backup before major changes like this, so you have the ability to restore to a known working state in the unlikely event something goes very wrong.
Estou numa situação empolgante: preciso fazer a atualização da versão v2.1.0.beta2 +119 para a 2.4.0.beta4.
Naturalmente, estou um pouco nervoso com isso, então gostaria de saber se você poderia me orientar sobre como fazer um backup completo?
Estamos rodando isso em um container Docker. Também realizamos backups diários pelo painel de administração, mas, se eu tentar fazer a atualização com ./launcher rebuild app e algo der errado, como posso voltar para a versão anterior (que estava funcionando)? Pelo que pude ver, os backups contêm apenas o SQL do banco de dados Postgres. Todas as imagens estão armazenadas em outro lugar, no S3.
Se você puder fornecer alguma orientação, ficaria muito grato.
Sim, isso deve funcionar sem problemas. É altamente improvável que uma reconstrução falhe e, se isso acontecer, nada será quebrado. Seu site ficará indisponível, mas os dados estão seguros em um local de armazenamento persistente (não em um contêiner Docker).
Fazer um backup é uma ótima ideia (sempre faça backups) e, sim, seus uploads não são baixados para o backup. Seu banco de dados referencia os uploads no S3 e continuará fazendo isso no backup e após a restauração. Portanto, não é necessário baixá-los; eles já estão seguros no S3.
Se algo der errado com a reconstrução, poste a saída do log aqui!