Update database from 1.8.007 to current (21 - github)

David_C_Rankin 2021-11-25 06:25:09 UTC #1

Ralf, All,

I have nursed my trusty 1.8.007 install as far as I can. I need to move forward in time to the current release and don’t know if I will need to transition through incremental versions to move the database forward?

I toyed with 14 and 16.1, but always reverted due to pixelegg issues and loss of screen real estate.

From what I gather the egw update is fairly straight forward, install composer, grab clone the current repository, download and install the needed deprecated apps from 17.1, but what of the database backend? (MySQL - now MariaDB).

Will I need to do anything special or need to install incrementally to move my installation forward? Thanks for any help or suggestions you can give.

RalfBecker 2021-11-25 07:36:16 UTC #2

Hi David,

That is not the recommended and by far the most complicated way for an EGroupware installation!

You need eg. the npm stuff …

The recommended way on a Linux distribution is to use our packages, which install a set of docker Container:

The wiki also explains that you can and for an upgrade from before 14.1.004 you must install the deprecated API and other deprecated apps via their Linux packages (or clone them to /usr/share/egroupware on the host).

Give it a try with a clean new installation and test it. For the update you only need to do a DB backup inside EGroupware, rsync /var/lib/egroupware/default/{files,backup} to your new hosts /var/lib/egroupware/default/ and restore the backup via setup. (Remember you need the deprecated API to be able to update from before 14.1.003!)

The default installation comes with a MariaDB 10.4 running in a container, probably soon updated to 10.5.

Ralf

RalfBecker 2021-11-25 07:58:11 UTC #3

And of cause the push server and everything else coming as a container only: Collabora, Rocket.Chat, …

Even the developer install comes nowadays as a container.

Ralf

David_C_Rankin 2021-11-27 20:02:48 UTC #4

Oooohhh… Nuts…

Thank you Ralf for the reply. It warms the heart to see how well you have done and how far egroupware has come in the past 15 or so years.

Containers raise problems for the attorney requirement to safeguarding client information. Not for the information, but for the attorney’s responsibility to validate how the information is being handled and served. Containers composed by others are essentially black-boxes.

A server install allows for review and validation of what is run when keeping things under my control. To use a container approach I could validate and defend in the event of any problem, I would essentially have to use docker to compose the container from my site to begin with. (not the mention the additional overhead a contianerized apache and MySQL requires in addition to the native apache and MySQL already running)

Is there no way to continue to run current egw outside of a container? I’m not worried about it being a bit harder to do, or taking a bit longer to setup, I just need to be able to verify how the information is being handled.

If the current egroupware cannot be run outside a contianer, what would be the latest version that I can run from a self-hosted server similar to what I do now?

RalfBecker 2021-12-01 07:16:06 UTC #5

Not, if the Dockerfile is published, as for the containers we provide:

github.com

EGroupware/egroupware/blob/21.1/doc/docker/fpm/Dockerfile

################################################################################
##
## EGroupware FPM container using Ubuntu 18.04 and PHP 7.3 from ondrej/php PPA
##
################################################################################
FROM ubuntu:20.04
MAINTAINER rb@egroupware.org

ARG VERSION=dev-master
ARG PHP_VERSION=7.4

# keeping build-arg in environment for entrypoint.sh
ENV VERSION=$VERSION
ENV PHP_VERSION=$PHP_VERSION

RUN apt-get update \
	&& apt-get install -y software-properties-common \
	&& LC_ALL=C.UTF-8 add-apt-repository -y ppa:ondrej/php \
	&& apt-get update \
	&& bash -c "apt-get install -y php$PHP_VERSION-{cli,mysql,gd,xsl,bz2,opcache,apcu,tidy,zip,bcmath,mbstring,smbclient,ldap,curl,fpm,pgsql,gmp,memcached}" \

This file has been truncated. show original

The Dockerfile also shows what you need to do to install EGroupware directly on the host.

Problem is not to run EGroupware outside a container, but the knowledge to do so.

Ralf

StefanU 2021-12-01 13:47:31 UTC #6

Hi David.

Not necessarily.
The EGroupware containers essentially contain only the EGroupware sources and PHP.
You can enter the running container, then find yourself on the shell and can inspect it just as you do on your current system.

From:

docker exec -it egroupware bash
Enter the container egroupware.
Changes in the container are discarded by an update or recreation of the container!

Overall, a Docker installation brings many advantages. Especially for security and speed.
Especially important: We develop on certain versions of PHP, MariaDB (…) and deliver the containers in exactly the same way. Everything fits together, is secure and fast.
Collabora Online, Guacamole, Rocket.Chat, Push… All this is only possible on the basis of containers.

Here is something else to read:

Yes, first of all right. You need more resources.

But let’s be honest. Even a full installation is still very small and requires little RAM/CPU compared to other systems (Microsoft…).
It simply doesn’t work to meet increased demands with resources from 15 years ago.

I recommend you: Just install EGroupware with docker (old PC, small vServer, …) and take a look.

Stefan