Are upgrade instructions AWS Standard Edition 5.0.2(5) to 6.0.0 available?

[Ralf_Lukner (Ralf Lukner MD PhD)]

@Ralf_Lukner

version: ‘3.1’ services: openemr: restart: always image: openemr/openemr:5.0.2 ports: - 80:80 - 443:443 volumes: - logvolume01:/var/log - sitevolume:/var/www/localhost/htdocs/openemr/sites environment: MYSQL_HOST: ‘xxxxxxxxx.yyyyyyyyyy.us-east-1.rds.amazonaws.com’ MYSQL_ROOT_USER: openemr MYSQL_ROOT_PASS: ‘zzzzzzzzzz’ MYSQL_USER: openemr MYSQL_PASS: ‘zzzzzzzzzzzzz’ OE_USER: admin OE_PASS: ‘zzzzzzzzzzzz’ volumes: logvolume01: {} sitevolume: {}

See Brady’s comment above … “In the case of the ssh certs though, there is no shared volume to retain that. So will need to replenish (just copy in the certs from the “old” docker) the ssl certs in your docker after the docker-compose up command.”

So, based on my understanding, I will modify my docker-compose.yaml file as follows:

version: '3.1'
services:
  openemr:
    restart: always
    image: openemr/openemr:6.0.0
    ports:
    - 80:80
    - 443:443
    volumes:
    - logvolume01:/var/log
    - sitevolume:/var/www/localhost/htdocs/openemr/sites
    environment:
      MYSQL_HOST: 'xxxxxxxxx.yyyyyyyyyy.us-east-1.rds.amazonaws.com'
      MYSQL_ROOT_USER: openemr
      MYSQL_ROOT_PASS: 'zzzzzzzzzz'
      MYSQL_USER: openemr
      MYSQL_PASS: 'zzzzzzzzzzzzz'
      OE_USER: admin
      OE_PASS: 'zzzzzzzzzzzz'
volumes:
  logvolume01: {}
  sitevolume: {}

I have been down this road before and it was not a happy experience (see Planning for OpenEMR 5.0.2 release - OpenEMR Development - OpenEMR Community (open-emr.org)).
I think what I need to do use images of production system to create a new EC2 and RDS instance and then try to migrate such a “test” system until I have a reliable and tested upgrade procedure.
RBL