# Planning for OpenEMR 5.0.2 release

**URL:** <https://community.open-emr.org/t/planning-for-openemr-5-0-2-release/11858>\
**Category:** OpenEMR Development\
**Created:** [March 29, 2019, 7:26am UTC](https://community.open-emr.org/t/planning-for-openemr-5-0-2-release/11858 "2019-03-29T07:26:25Z")\
**Posts on this page:** 1\
**Showing post:** 80

<div class="post-metadata">

**Author:** ![Ralf\_Lukner](https://community.open-emr.org/user_avatar/community.open-emr.org/ralf_lukner/32/11962_2.png) [@Ralf\_Lukner](https://community.open-emr.org/u/Ralf_Lukner)\
**Post date:** [August 12, 2019, 5:53am UTC](https://community.open-emr.org/t/planning-for-openemr-5-0-2-release/11858/80 "2019-08-12T05:53:52Z")

</div>

> [@brady.miller](#):
>
> Very cool. Make a backup ec2(along with RDS) of your instance and then try the below upgrade on that (ensure you use a backup RDS or else it will upgrade your original database).
> 
> To do the upgrade will involve following steps:  
> **Step 1** - Go into directory
> 
> ```auto
> cd /root/openemr-devops/packages/standard/
> 
> ```
> 
> **Step 2** - Modify docker-compose.yaml file  
> Change the `image: openemr/openemr:5.0.1` line in docker-compose.yaml to:  
> `image: openemr/openemr:5.0.2`  
> **Step 3** - Bring in the new docker (which will auto-upgrade it)
> 
> ```auto
> docker-compose up -d
> 
> ```
> 
> **Step 4** - Ensure it worked by checking the log
> 
> ```auto
> docker logs standard_openemr_1
> 
> ```

Ok. So I have an AWS EC2/RDS(MySQL) test system now thanks to substantial help from everyone above.

Now I’m trying to do the upgrade on the test system as explained by @brady.miller above …  
Step 1 - DONE: sudo bash … then cd /root/openemr-devops/packages/standard/ as given by brady.  
Step 2 - DONE: Modify docker-compose.yaml file  
Change the `image: openemr/openemr:5.0.1` line in docker-compose.yaml to:  
`image: openemr/openemr:5.0.2`  
Step 3 - DONE:  
**root@ip-10-0-1-179** : **/root/openemr-devops/packages/standard** # /root/openemr-devops/packages/standard/docker-compose up -d

Removing elegant\_goldstine

Removing nervous\_elion

Removing affectionate\_carson

Removing epic\_kalam

Removing eloquent\_mcnulty

Pulling openemr (openemr/openemr:5.0.2)…

5.0.2: Pulling from openemr/openemr

050382585609: Pull complete

4d61f28ee280: Pull complete

76e61a049383: Pull complete

bf5110788d99: Pull complete

0f871c9e49bb: Pull complete

61236122513d: Pull complete

343af72d1676: Pull complete

3ab4fbedcac6: Pull complete

9af2c76c95e8: Pull complete

b8fe35ac4f01: Pull complete

553e8e64c900: Pull complete

9674cacacb05: Pull complete

9ce5ad550ce6: Pull complete

Digest: sha256:616140a6039bb381ef1efecb573e4e30aa2e207c14339818d205664235c05430

Status: Downloaded newer image for openemr/openemr:5.0.2

Recreating standard\_openemr\_1 …

Recreating standard\_openemr\_1 … done

**root@ip-10-0-1-179** : **/root/openemr-devops/packages/standard** #OpenEMR Development

Then  
docker logs standard\_openemr\_1

Plan to try an upgrade from 0 to 1

Attempting upgrade

Start: Processing fsupgrade-1.sh upgrade script

Start: Upgrade to docker-version 1

Start: Ensure have all directories in default

Completed: Ensure have all directories in default

Start: Update new directory structure in default

Completed: Update new directory structure in default

Start: Clear smarty cache in default … etc. etc. (lots of information)…

……  
Completed: Upgrade database for default from 5.0.1

Completed: Upgrade to docker-version 1

Completed: Processing fsupgrade-1.sh upgrade script

Completed upgrade

Setting user ‘www’ as owner of openemr/ and setting file/dir permissions to 400/500

Default file permissions and ownership set, allowing writing to specific directories

Removing remaining setup scripts

Setup scripts removed, we should be ready to go now!

Love OpenEMR? You can now support the project via the open collective:

\> [Contribute - Open Collective](https://opencollective.com/openemr/donate)

Starting cron daemon!

Starting apache!

AH00558: httpd: Could not reliably determine the server’s fully qualified domain name, using 172.18.0.2. Set the ‘ServerName’ directive globally to suppress this message

Looks like it worked.

Now try it out…  
Seems to work well. I will test this test system out for a few days before I upgrade the production system.

Thank you, everyone!!  
–Ralf

---

_[View the full topic](https://community.open-emr.org/t/planning-for-openemr-5-0-2-release/11858)._