remove Vagrant

[pdurbin]

I sent the following message ( https://groups.google.com/g/dataverse-community/c/y1_JCWN44II/m/FFjQTkJ4AwAJ ) a couple weeks ago:

From: Philip Durbin philip_durbin@harvard.edu
Date: Mon, 14 Aug 2023 16:38:21 -0400
Subject: Vagrant on chopping block
To: dataverse-community@googlegroups.com

I added a Vagrant environment way back in the DVN 3 days but it's become a
bit of a maintenance burden.

We're in the middle of bumping the version of Payara, Java, and Solr. Each
time, we go back to the Vagrant scripts and tweak them.

These days I've switched to Docker and I don't even have Vagrant installed
on my three year old laptop. I think I've convinced myself to just delete
Vagrant stuff from the code base.

I'm writing mostly to give a heads up. If anyone out there wants to
maintain the Vagrant code, maybe it can be moved to another repo? If you
have an opinion about Vagrant, please let me know.

Thanks,

Phil

p.s. Here's our current writeup of Vagrant:
https://guides.dataverse.org/en/5.14/developers/tools.html#vagrant

As implied above, these days we're encouraging Docker instead:
https://guides.dataverse.org/en/5.14/container/dev-usage.html

--
Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin

There were no objections and it has been annoying to fiddle with Vagrant files while we upgrade Payara and Solr. We aren't even testing the Vagrant changes (it would have complained about the Java 17 upgrade if we had). I don't even have Vagrant installed. Let's remove it. It will reduce the number of files we need to change when upgrade Java, Payara or Solr.

If people really want to use Vagrant they can probably use https://github.com/GlobalDataverseCommunityConsortium/dataverse-ansible/blob/develop/Vagrantfile or create their own repo.