Hello,
would there be a --preferably automated-- procedure to backup the content data (i.e., presumably the db), then to restore it in a fresh install?
If not, what would be the best (cleanest, easiest, etc.) option for that?
The best couple of ways I can think of are:
I/
(a) to manually dump the db regularly,
(b) (in case restoring is required) run the installer in a fresh environment, then restore the dump manually in the newly installed Postgres instance.
The problem is, could the manual process mess with settings, or config files that would not be adequately updated?
Alternatively:
II/
(a) dump the db
(b) the dump is restored in a new Postgres instance first, then
© the installer is run, assuming it can be forced to use this db instance.
But a similar question occurs with regard to the internal settings and config files.
Sorry for cross-posting on GitHub, but I can not find the topic being addressed anywhere. Apologies if that is the case. If so, it would be very kind of you to point me in the right direction.
Cheers,
JP
.