Hi @gutiersa ,
Regarding php7.2 and mysql8:
This is another win for dockers.
OpenEMR 5.0.1 is compatible with PHP 7.2 , which was much easier for us to make compatible because of the demo farm (which uses dockers) having demos for PHP 7.2 here:
Ubuntu 18.04 with PHP 7.2 openemr demo
Alpine Edge with PHP 7.2 openemr demo
OpenEMR 5.0.1 with patch 3 is compatible with mysql-8
Note mysql8 breaks installation, so need to await the new 5.0.1 builds (that will have patch 3 in them); at this point only the 5.0.1 docker has patch 3 in it. The only caveat is that need to set default-authentication-plugin=mysql_native_password in the mysql8 server.
Note that getting mysql8 to even work was made much easier with dockers, since I used the docker development environment (this allows use to test code on php 7.1/7.2(with and without ssl) and all 9 supported version of mysql/mariadb):
openemr/README.md at master · openemr/openemr · GitHub
As an aside, after going through above mysql8 work, it really looks like mariadb and mysql are beginning to diverge, which is interesting. For example, mariadb 10.3 (their soon to be released version) does not require the default-authentication crud and does not reserve groups and does still allow creating a user and granting permissions at the same time (note these were the 3 issues that needed to be addressed to support mysql8).
Regarding globals.php error log:
Which line in globals.php are you referring to? If I know that, I can provide more background on it.
Regarding docker for your emr
Heck yes. Note that 4 of the 5 AWS Cloud offerings and the Appliance are using dockers. Recommend installing docker and docker-compose on your computer and playing around with it. For example, here is a docker compose I just created that should get you started with openemr, mysql (version 8 at that), and phpmyadmin:
https://gist.github.com/bradymiller/a882618169f61b7316e4ad4067cf69eb
Which you can test it quickly here:
If you take this script locally and rename it to docker-compose.yml, then in same directory do:
docker-compose up -d
Then it will build it for you (takes a minute or so)
And then you can tear it all down with (delete everything) with:
docker-compose down -v
To give you a visual of what is happening when dockers are going, type:
docker ps -a
You can also stop them all without removing anything:
docker-compose stop
and start them
docker-compose start
And lets say you don’t want phpmyadmin going for security reasons, then
docker-compose stop phpmyadmin
and could even remove the restart: always line for phpmyadmin in docker-compose.yml to ensure it does not start when host does shutdown/restart
And the ports for each service in docker-composer.yml are where things map to; note now using 8080-8082, but can make them 80,443,8081 if wish, or anything else if wish.
The one thing you need to get used to is sometime needing to work in the docker themselves, which is easy once you figure out how to do it. You can learn more about the openemr docker here also:
https://hub.docker.com/r/openemr/openemr/
-brady