Closed stephenwaite closed 2 years ago
openemr v5.0.1 still trucking :)
thinking this makes sense to get rid of 3.9
plus we'll still be able to check on 5.0.1
and 5.0.2
through ubuntu 18
@stephenwaite , Looks like you have figured out demo tetris :) Looks good and ready to come in. After bring in, then rec making the wiki changes.
One more thing to mention and something I have been burned on before with this mapping file. It is a tab delimited file, so need to ensure your editor doesn't convert the tabs to spaces or everything basically explodes :)
thanks for the help @bradymiller , phew :)
the wiki's are updated now so will hopefully match tmrw
hi @stephenwaite , Super awesome to get a PR in the demo docker repo!
For the demos, can check out the ip mapping script to see what they are used. The eight demo docker is mapped to these 4 demos (check out the far right to see their descriptions): https://github.com/openemr/demo_farm_openemr/blob/master/ip_map_branch.txt#L31-L34
So first 2 are based on dev and will state that will no longer work since PHP is < 7.4: https://www.open-emr.org/wiki/index.php/Development_Demo#Alternate_Demo_.28Alpine_3.12_-_uses_php_7.3.29
And the second 2 are for 6.0.0 and are working: https://www.open-emr.org/wiki/index.php/Development_6.0.0_Demo#Demo_.28Alpine_3.12_-_uses_php_7.3.29
So, this should stay as 7.3 (ie. should not bring this PR in).
Generally when need more demos (for new version release or something else), I generally then take these old ones and use them and change their os's if needed. It's basically like playing tetris with 12 demo dockers with 46 demos. When need new docker or docker set, I basically look through ip_map_branch.txt to see what demos are now outdated, then change them and remove/add them from the wiki. If needed, can also add more demos to each docker, but avoid that since 46 is likely enough. Btw, am still trying to figure out how to have a demo with 1 million patients (it is going to be like the 3 MU3 demos where the 1 million patient database is a capsule and then get updated to most recent codebase); got an older laptop that plan to run 10 x 100K runs, which will likely take 10 days or so :) .