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
update Vagrantfile to use CentOS-8.2 and Payara5 #7153
Conversation
I'm giving this a try. Assuming is works we'll probably want to back out of some of my doc changes at a7c986d (screenshot below) when I de-emphasized the use of (broken at the time) Vagrant. |
I tried this on Friday but hit a snag (below). I'm on Vagrant 2.2.3.
|
@pdurbin did you try Vagrant 2.2.9? |
No. |
Ok, I upgraded and it works great. Thanks, @donsizemore !
|
This is almost ready for QA but we should remove the line in the docs about Vagrant being broken. I made this pull request for that: uncch-rdmc#54 I looked thought the other docs changes above: #7153 (comment) Now that we have nice for-production solutions like dataverse-ansible, I don't feel the need to promote Vagrant as much in the Installation Guide. The Vagrant enthusiasts will find the Vagrantfile and I think that's enough. @donsizemore heads up about the pull request above. Thanks. |
remove warning about Vagrant being broken IQSS#6849
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works great! I pasted some output showing Payara at #7153 (comment)
Thanks. @donsizemore !
What this PR does / why we need it: updates Vagrantfile to use CentOS-8.2 and Payara5
Which issue(s) this PR closes:
Closes #6849
Special notes for your reviewer: none
Suggestions on how to test this:
vagrant up
Does this PR introduce a user interface change? If mockups are available, please link/include them here: no
Is there a release notes update needed for this change?: no
Additional documentation: plenty of code comments for the curious