Application Name:
Platform 2.7.x and Reference App 3.2.1
Version Number: 2.7.0
Question:
Hello, I am able to run using the sdk: openmrs-sdk:run
I’d like to be able to package the distribution for deployment across servers; are there instructions on how to move from the sdk to a deployment package that can be distributed.
the target system would be running tomcat and mysql.
While I have not used a CI/CD to deploy any openmrs-sdk based distribution on a remote server. I always preferred to make use of the distro-reference implementation to leverage the simple Docker method.
I once manually deployed the SDK-based implementation on the server, making sure the process ran in the background and prevented it from quitting when I exited the terminal sessions.
Now, all instances we have on remote environments are Docker-based.
I will also advise using Docker. If you prefer, there are experts here who can give you instructions.
@ibacher@raff@dkayiwa@dennis
Sure, the environment we are looking at won’t be docker initially; we are looking at a cloud platform - most likely AWS; I have a lot of experience doing CICD in different evironments and need to understand the best way to deploy the platform; the reference app is pretty easy to deploy after you run the sdk. We opted to use external mysql and tomcat to allow us to configure the app in AWS. However, I don’t want to re-install but rather transfer the outputs of the SDK directly. I would be open to any notes or comments on the best way to do this. Down the road we may consider EKS if not docker once we have integrated external systems.
Thank you for your help, its much appreciated.
@ibacher@raff@dkayiwa@Dennis
thank you, this is useful information; our initial deployment is on basic servers - so if I understand or figure out how to deploy sdk to a basic server as a production deployment, I can then look at the requirements for running in the cloud.
I am able to setup a local Kubernetes cluster based on AWS; but our immediate need is to build a deployment process for moving an sdk-based installation to a server in the cloud; we can then look at the requirements for running inside a container - much more configuration and possible changes to the omod modules in that case; that would only be looked at as a secondary task.