![]() ![]() So, even on most modern linux systems, we use apt (on Ubuntu, for example) to pull the repo. However, even with the “older unix way” this method often does not provide a complete solution because there are often shared libs in system, shared lib user directories, and more which are not a part of the distribution directory, and there are etc files which are not in the distro root directory, etc. Using github as the repo is a cleaner solution that the older unix'y way of “tarring the whole darn thing up” and “moving the whole darn thing” over to another server. Then, restore your full backup, including uploads (from the command line in the container). It might be possible to edit your container yml file and rebuild from scratch, but the more conventional way is to just save your:Īnd then edit your container yammy, clone the discourse-docker repo and rebuild. These Discourse docker images are built as docker images and as a part of Docker they don’t “live” in /var/discourse but are built there and then moved to docker as docker images. One of the main reasons is that when you build / bootstrap Discourse, it (launcher as I recall off the top of my head) will check if a base Discourse container (image) exists and pull down the base discourse Docker image (if not) and start up that base docker image into a container.Īfter that base git pull, the build process will build another docker image (the app)īoth of these docker images (the base image and the app image) do not exist inside /var/discourse, so tarring up /var/discourse is only a partial “solution” (using this term loosely). ![]() You cannot simply “tar up” the /var/discourse directory and move it to another machine, untar it, and start the discourse app. Therefore I wanted a more “complete” 1to1 “hardcopy” way to backup. I am aware of these instructions these don’t work for me. That doesn’t move the whole /var/discourse folder. Why is postgres updated from version 10 to version 12 by simply copying the whole folder from one server to another? I must be doing something wrong.Ĭould you please kindly share instructions on how to backup the whole discourse app on one server and move it to another server? Why are these file permission issues introduced? pg_ctl: could not start server Examine the lo[FAILput. Starting PostgreSQL 12 database server: main Error: /usr/lib/postgresql/12/bin/pg_ctl /usr/lib/postgresql/12/bin/pg_ctl start -D /shared/postgres_data -l /var/log/postgresql/postgresql-12-main.log -s -o -c config_file="/etc/postgresql/12/main/nf" exited with status 1: 10:20:10.501 UTC FATAL: database files are incompatible with server 10:20:10.501 UTC DETAIL: The data directory was initialized by PostgreSQL version 10, which is not compatible with this version 12.2 (Debian 12.2-2.pgdg100+1). Guess some fixes: chown -R postgres.postgres /etc/postgresqlĬhown -R postgres.postgres /shared/postgres_*Ĭhown -R postgres.postgres /var/lib/postgresqlĬhown -R postgres.postgres /var/log/postgresqlĬhown -R redis.redis /etc/redis/nfīut did not help. Starting PostgreSQL 12 database server: main Error: The cluster is owned [FAILoup id 116 which does not exist. launcher start app service postgresql statusġ2/main (port 5432): service postgresql start rsync -recursive -links -hard-links -safe-links -owner -group -perms -times -delete -sparse -compress -partial /var/production-backup/var/discourse/ /var/discourse ![]() ![]() How to backup and restore a whole /var/discourse folder?ĭue to issues with the usual backup and restoration process, I was wondering if I could backup the whole /var/discourse folder and re-use it on another server. ![]()
0 Comments
Leave a Reply. |