add lip-computing/dataverse to prep.rst#8965
Conversation
Added LIP's repo with resources for an advanced installation as proposed by Philip Durbin.
pdurbin
left a comment
There was a problem hiding this comment.
https://dataverse-guide--8965.org.readthedocs.build/en/8965/installation/prep.html#advanced-installation looks good!
I added #8963 to the "closes" line in the PR description (so that the issue get closed when we merge the PR).
Heads up to @donsizemore @poikilotherm @4tikhonov and @lwo that @zbenta agreed that for a future PR, we might want to give each installation option more room on the page than just a link. A paragraph perhaps. Or maybe even move to a different page. For now we just wanted to get the link in there.
I was going to do so @4tikhonov , but @pdurbin Suggested I added it on the second position since the puppet version was very old, but I can change it if you guys prefer. |
|
I like the current order, which puts the older, less-maintained options at the bottom. @4tikhonov certainly we could get more organized, list maintainers, etc. Good ideas for phase 2! 😄 If someone wants to go ahead and create an issue for future improvements, please go ahead (and drop a link in here please). We can pick up the conversation there. This is just a one line change so I'm going to merge it. Thanks, all! 🚀 Update: Now that the PR is merged, you can see the change at http://preview.guides.gdcc.io/en/develop/installation/prep.html |
Added LIP's repo with resources for an advanced installation as proposed by Philip Durbin.
What this PR does / why we need it:
Added some new installation method to the advanced installation documentation.
Which issue(s) this PR closes:
The unavalabilty of a recipe for an advanced installation with all the resources needed to deploy a full functioning dataverse service with a fault tolerant architecture
Closes #8963
Special notes for your reviewer:
Suggestions on how to test this:
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
Is there a release notes update needed for this change?:
Additional documentation: