I would like to first get a 1:1 copy running, secure it via a full backup, and then determine how to start the update process without destroying the instance. Once I have found a working method, the production instance will also be updated.
The current difficulty is:
How do I first create a 1:1 copy of my old version, including the old PG database and old plugins?
As a beginner, I am very grateful for any hints and/or links.
Thank you very much for your time and best regards,
Richarde
As I understand it, the backup does not include any software, so plugins and their software versions, nor does it include Discourse itself with its version. Therefore, it is not suitable for the above issue.
Fortunately, the plugin that was preventing our update is now compatible again with the current version of Discourse, so I was able to set up a new server with the latest version and restore our backup there.
Nevertheless, it could be very useful for some (including our community during the time when the plugin was not compatible with the software) to know how to set up a test instance as a 1:1 copy to test further steps in a safe environment without affecting production.
The basic process looks pretty straightforward, though there are many comments offering modified approaches and command parameters. I haven’t done it myself. If I had to, I suppose I’d start with the basics and see how it goes. Several possible gotchas are discussed in the comments.
The quoted one from myself is what I tried, and didn´t Work.
Making a 1:1 with a Snap via the Provider, disabling https.
I tried a lot also changing Conf. via rails but couldn´t get it to work, so the Way via snap isn´t working for me at all. So I´m asking here, for a way how to do it. (even if i solved my Problem already, this might be helpful in the future)
Yes, which again leads to updates, why this shouldn´t work.
