-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Vagrant box reference to readme #48
Conversation
Merge develop into master for 1.0.35/SITE 3.1.19 Sept2018 Release
Merge Develop into Master for Oct 2018 3.1.20 Release
Merge develop into master for SITE Nov 2018 3.1.21 Release / 1.0.36
Hi Thanks! |
@drbgfc it includes both the reference-ccda-validator and code-validator-api repositories as git submodules (so they will always be up to date). When the vagrant box builds, it also downloads the referenceccdaservice.war from the github release page. None of the validator resources are actually included in the vagrant github project. The vagrant up command fetches what it needs and moves files around from the respective git submodules. You can see here what it does: I believe it does include scenarios? This is a screenshot from the vagrant machine running. |
Great thanks, just confirming. We would love to have a setup like this that also includes the vocabulary but we can't due to licensing issues, although there may be a way in the future to resolve that so it's cool that this work was done. So I wanted to make sure, although awesome, that that was not done to protect you. I'll inform the ONC about this and don't forsee any issues with the reference. |
FYI: I am in discussion with the ONC on this matter |
No description provided.