-
Notifications
You must be signed in to change notification settings - Fork 494
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
Get Vagrant working on Payara and with updated installer #6849
Comments
Merged
donsizemore
pushed a commit
to uncch-rdmc/dataverse
that referenced
this issue
Jul 31, 2020
pdurbin
added a commit
that referenced
this issue
Aug 3, 2020
donsizemore
added a commit
to uncch-rdmc/dataverse
that referenced
this issue
Aug 3, 2020
remove warning about Vagrant being broken IQSS#6849
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Vagrant appears in our docs in a number of places (screenshot below) and has a prominent place in the "Choose Your Own Installation Adventure" section of the Installation Guide:
I took a swing at getting our Vagrant code working with Payara and the changes to the installer scripts but it turns out to be enough effort that a dedicated issue is warranted.
Here's what I learned or was reminded of:
My plan is to commit what I have which at least gets rid of references to Glassfish 4.1. Moving forward, I would suggest the following:
Here are the many mentions of Vagrant:
The text was updated successfully, but these errors were encountered: