extern/egroupware
1
0
Fork 1
mirror of https://github.com/EGroupware/egroupware.git synced 2024-11-22 07:53:27 +01:00
Code Issues Packages Projects Releases Wiki Activity

add Nginx Let's Encrypt instruction link

Ralf Becker 2019-08-21 09:09:04 +02:00
parent cb5be7a3c7
commit e9b1f6fde6
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
Update-recommendations-and-troubleshooting.md

@ -2,20 +2,21 @@
> **If something goes wrong with the update, it is in almost all cases related to the Apache or Nginx configuration on the host, and NOT Docker and the running containers!**
If you are not familiar with your Apache/Nginx configuration (including https), or need to ensure only a minimal downtime, the recommendation will be always to do the **painless new installation** on a new host and then an **migration of your database and files** to the new host! Same is true if your old hosts version is no longer supported by from it distribution.
If you are not familiar with your Apache/Nginx configuration (including https), or need to ensure only a minimal downtime, the recommendation will be always to do the **painless new installation** on a new host and then an **migration of your database and files** to the new host! Same is true if your old hosts Linux version is no longer supported from it's distribution.
# Requirements for the update to succeed
The update operates under the assumption you have NOT changed any of the following:
* files or backup directory (/var/lib/egroupware/default/files or /var/lib/egrouware/default/backup)
* your database runs on the host AND you use "localhost" as "db_host in header.inc.php
* your EGroupware runs under http(s)://your.domain/egroupware (Setup >> Konfiguration >> Webserver URL: /egroupware).
* with the exception of MariaDB/MySQL no other service (LDAP, IMAP, PostgreSQL) uses a host-name of ***localhost***
> If you changed anything of the above, you either need to change it back to the default locations, or you need to fix your installation after the update.
> ***EGroupware will fail after the update without any further changes!***
# How to migrate your data from an existing 17.1 or older installation
1. do a new installation as described for the distribution of the new host
2. enable https using Let's Encrypt following the exzellent instructs from eg. [Digital Ocean](https://www.digitalocean.com/community/tutorials/how-to-secure-apache-with-let-s-encrypt-on-ubuntu-18-04)
3. make a database backup inside EGroupware using ***Administration >> Database backup and restore***
2. enable https using Let's Encrypt following the exzellent instructs from eg. Digital Ocean for [Apache](https://www.digitalocean.com/community/tutorials/how-to-secure-apache-with-let-s-encrypt-on-ubuntu-18-04) or [Nginx](https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-18-04)
3. make a database backup inside your old EGroupware using ***Administration >> Database backup and restore***
4. rsync the files and backups from the old installation to the new server, run on the new server the following commands:
```
rsync -av --delete root@<ip-of-old-server>:/var/lib/egroupware/default/ /var/lib/egroupware/default/