(warning: language)
https://youtu.be/gbIv7W7rhx4?t=36s
We have now reached out to the community in various ways, and we are finding out that everything that we have been doing is incorrect.
Everything
So, according to information that has been gathered, we have been urged to move our efforts away from the OpenMRS core. Instead, we should be using the standalone application. Doing so, we will be able to work against individual modules and use the standalone as an engine of sorts, instead of trying to build and configure the entirety of OpenMRS just to test against modules.
This should speed things up significantly. In the course of today's class we have most of the OpenMRS team on the same page, to my knowledge. It should be a very brief process for us to all get started and working on a specific issue, which is very exciting considering all of the difficulties thus far.
Briefly, the Process:
Set up is very simple for a Ubuntu.
You will need:
- Vagrant
- OpenMRS Reference App: https://github.com/openmrs/openmrs-distro-referenceapplication
- VirtualBox
- Maven
Just check out the OpenMRS Reference App from GitHub, cd into the directory, run "mvn clean install" and then run "vagrant up".
Done. That's it. It will install everything else that you need, including the image for Ubuntu 12.xx (which Austin and I found to be interesting at the least). We only wish we had known this sooner.
Now that I have written this out, I have managed to stumble across a more comprehensive guide on the documentation wiki. How silly of me. At any rate, there is much to be done by Monday and this post should have been finished sooner, but it is what it is. You know what they say (warning: language).
No comments:
Post a Comment