From cba7fe4cdd96e05935bd779d438e1c5caab3d067 Mon Sep 17 00:00:00 2001 From: Ralf Becker Date: Sun, 15 Sep 2019 11:23:21 +0200 Subject: [PATCH] move PostgreSQL stuff to "distro specific" page, as it's not trouble-shooting or recommendations --- Update-recommendations-and-troubleshooting.md | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/Update-recommendations-and-troubleshooting.md b/Update-recommendations-and-troubleshooting.md index da66017..d71fe39 100644 --- a/Update-recommendations-and-troubleshooting.md +++ b/Update-recommendations-and-troubleshooting.md @@ -25,17 +25,6 @@ chown -R 33:33 /var/lib/egroupware/default 5. log into the new EGroupware using the generated ***sysop*** user and go to ***Administration >> Database backup and restore*** and restore the last backup you rsynced to the new server 6. you can repeat steps 3. to 5. multiple times, until you are ready to use the new system productively -# How to install with PostgreSQL -While an update of a PostgreSQL instance works similar to MariaDB/MySQL, a new installation does not happen automatic! -1. Edit /etc/egroupware-docker/docker-compose.yml and add the following to the [environment section](https://github.com/EGroupware/build.opensuse.org/blob/master/server:eGroupWare/egroupware-docker-19.1/egroupware-docker/docker-compose.yml#L44): -``` -- EGW_SKIP_INSTALL=true -``` -2. start the containers as usual with: ```docker-compose up -d``` -3. Go to http://example.org/egroupware/setup/ and do a manual installation - -> Keep in mind, that you can NOT use ```localhost``` to address a service eg. PostgreSQL inside the container, as it does NOT refer to the host, but the container itself. You have to use the IP address of the host or the docker0 bridge AND make sure the service is not just bound to localhost! - # Trouble-shooting a not working installation after the update What to do if you can not access EGroupware after the update: