Open pdurbin opened 1 year ago
A few thoughts:
33
instead of a 10
is time well spent.I would leave the install guide alone. Anyone looking at the prerequisites list will be intimidated regardless of anything else, much less getting to the 'going live' part. Speaking for myself, as someone who has yet to successfully install Dataverse, getting a containerized build script to handle the install would be ideal to simplify things and aid in adoption of the software. The fact that Dataverse seems to be exclusively developed using a non-containerized RedHat environment is a major barrier to 'simplifying' the install process.
I will revisit the Docker script I was working on with Windows 10 since I upgraded to Windows 11, which 'supposedly' has the systemd support needed in Windows Subsystem for Linux to possibly run the Dataverse from Docker scripts. Manually installing software requirements to manually setup a development environment seems like an ancient idea in our age of containers and virtualization.
Wow, the list is even longer now, especially with all the PID settings from PR #10234:
I introduced the "Going Live" steps in the installation guide in 4.6.2: https://guides.dataverse.org/en/4.6.2/installation/config.html#going-live-launching-your-production-deployment
Here's how the guides looked back then
Fast forward to today (including #8915 which isn't yet merged) and the list of steps before going live is quite long:
I'm concerned that people installing Dataverse will be intimidated by this long list. We should reorganize the Installation Guide a bit (let's say timeboxed to size of 10 or a full day) to put non-essential config elsewhere.
Candidates to move elsewhere:
I'm also open to other ideas but I hope I've captured the problem: a very long list to grok.
Or as @poikilotherm put it in a talk: