For training scenarios, on one server, you may want to deploy more than one DHIS2 instance at the same time
currently the dhis2-deploy-war uses the SAME /tmp/dhis2.war filename. therefore if the deploy script is run more than once, the download will step on one another. fix the file name in /tmp so that it is unique.
keep the war file somewhere and before downloaded compare md5 keys. only download if necessary
For training scenarios, on one server, you may want to deploy more than one DHIS2 instance at the same time
currently the dhis2-deploy-war uses the SAME /tmp/dhis2.war filename. therefore if the deploy script is run more than once, the download will step on one another. fix the file name in /tmp so that it is unique. keep the war file somewhere and before downloaded compare md5 keys. only download if necessary