Updated 20.1 Installation using egroupware docker RPM DEB package (markdown)

Ralf Becker 2021-05-25 12:44:47 +02:00
parent 3b486823bf
commit 879876c35a

@ -1,10 +1,10 @@
![](https://raw.githubusercontent.com/EGroupware/egroupware/master/api/templates/default/images/logo.svg) ![](https://raw.githubusercontent.com/EGroupware/egroupware/master/api/templates/default/images/logo.svg)
> Please also note the [release notes and distribution specific instructions](https://github.com/EGroupware/egroupware/wiki/20.1-Release-notes-and-distribution-specific-instructions) > Please also note the [release notes and distribution specific instructions](https://github.com/EGroupware/egroupware/wiki/20.1-Release-notes-and-distribution-specific-instructions)
The 20.1 installation is based on **Docker**, even for the DEB or RPM packages. The installation is based on **Docker**, even for the DEB or RPM packages.
The only requirement for the host system is Docker. The only requirement for the host system is Docker.
20.1 contains an additional push-server container and runs - for new installations - MariaDB 10.4 in a container too. Since 20.1 EGroupware contains an additional push-server container and runs - for new installations - MariaDB 10.4 in a container too.
**Docker and the database are installed with/by EGroupware in the correct versions. There is no previous installation necessary and also not reasonable.** **Docker and the database are installed with/by EGroupware in the correct versions. There is no previous installation necessary and also not reasonable.**
@ -20,7 +20,7 @@ The only requirement for the host system is Docker.
* EGroupware now uses TypeScript instead of plain JavaScript to ease client-side development * EGroupware now uses TypeScript instead of plain JavaScript to ease client-side development
* mail servers can be [configured to notify EGroupware about new mails](https://github.com/EGroupware/egroupware/wiki/IMAP-Push-Notifications) * mail servers can be [configured to notify EGroupware about new mails](https://github.com/EGroupware/egroupware/wiki/IMAP-Push-Notifications)
## 20.1 installation or update ## Installation or update
You first need to create a repository file for your Linux distribution and version and import the key for it. You first need to create a repository file for your Linux distribution and version and import the key for it.
I'll show it here in details for Ubuntu 20.04, for other distributions use [the above link](https://github.com/EGroupware/egroupware/wiki/20.1-Release-notes-and-distribution-specific-instructions). This is NOT necessary if you update, unless you use EPL before 19.1, which used a different repo. I'll show it here in details for Ubuntu 20.04, for other distributions use [the above link](https://github.com/EGroupware/egroupware/wiki/20.1-Release-notes-and-distribution-specific-instructions). This is NOT necessary if you update, unless you use EPL before 19.1, which used a different repo.
@ -34,13 +34,13 @@ sudo apt update
> We have now also a 20.1 Univention App available in their TestAppCenter, which [need to be enabled](https://docs.software-univention.de/app-provider.html#testing:test-app-center) before you get the 20.1 versions offered for updating as usual. > We have now also a 20.1 Univention App available in their TestAppCenter, which [need to be enabled](https://docs.software-univention.de/app-provider.html#testing:test-app-center) before you get the 20.1 versions offered for updating as usual.
### To upgrade in place from 19.1 ### To upgrade in place from 20.1 or 19.1
``` ```
apt upgrade apt upgrade
``` ```
> Use the default to NOT replace config-files, if you are asked. The update script takes care of all necessary changes! > Use the default to NOT replace config-files, if you are asked. The update script takes care of all necessary changes!
### For a new 20.1 installation ### For a new 21.1 installation
``` ```
apt install egroupware-docker apt install egroupware-docker
``` ```
@ -72,7 +72,7 @@ It will ask your EPL repo credentials, add them and the EPL image to your docker
* EGroupware files will be store (as usual) in /var/lib/egroupware on the host * EGroupware files will be store (as usual) in /var/lib/egroupware on the host
* it will start the following container: * it will start the following container:
1. **egroupware** Ubuntu 20.04 based container with PHP 7.3 FPM and the EGroupware sources 1. **egroupware** Ubuntu 20.04 based container with PHP 7.3 FPM and the EGroupware sources
1. **egroupware-push** PHP Swoole 7.3 endpoint of all websocket connections 1. **egroupware-push** PHP Swoole 7.4 endpoint of all websocket connections
1. **egroupware-nginx** Alpine based container with internal Nginx server 1. **egroupware-nginx** Alpine based container with internal Nginx server
1. **egroupware-watchtower** automatic updating all containers to new version, if available, at 4am daily 1. **egroupware-watchtower** automatic updating all containers to new version, if available, at 4am daily
@ -91,7 +91,7 @@ The following apps, which are deprecated since 14.3, are no longer part of 19.1:
They can however be installed from 17.1 repo or are kept in case of an update. They can however be installed from 17.1 repo or are kept in case of an update.
They will work with the 20.1 container, as docker-compose.yml passes /usr/share/egroupware from the host into the container as /usr/share/egroupware-extra. The container [entrypoint script](https://github.com/EGroupware/docker/blob/master/fpm/entrypoint.sh#L8) copies them into the volume shared between egroupware container and Nginx. They will work with the 21.1 container, as docker-compose.yml passes /usr/share/egroupware from the host into the container as /usr/share/egroupware-extra. The container [entrypoint script](https://github.com/EGroupware/docker/blob/master/fpm/entrypoint.sh#L8) copies them into the volume shared between egroupware container and Nginx.
This mechanism can also be used to add arbitrary third-party apps to an EGroupware running in a container: This mechanism can also be used to add arbitrary third-party apps to an EGroupware running in a container:
``` ```