-
Notifications
You must be signed in to change notification settings - Fork 488
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
4.3 installer improvements #3017
Conversation
specifies that this installation isn't going to use tworavens.
(still need to change the note in the installers guide)
…i blocking" script.
Fixed typo
Corrected information about the installer.
@@ -21,7 +24,12 @@ Execute the installer script like this:: | |||
# cd dvinstall | |||
# ./install | |||
|
|||
The script will prompt you for some configuration values. If this is a test/evaluation installation, it should be safe to accept the defaults for most of the settings: | |||
**NEW in Dataverse 4.3:** It is no longer necessary to run the installer as root! |
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.
(Do note, that you want the Glassfish directory to be owned by the same user that will be running Glassfish. And you most likely won't need to run it as root. The only reason to run it as root would be to be able to run the application on the default HTTP(S) ports 80 and 443, instead of 8080 and 8181. However, an easier, and more secure way to achieve that would be to instead keep Glassfish running on a high port, and hide it behind an Apache Proxy, via AJP, running on port 80. This configuration is in fact required if you choose to have your Dataverse support Shibboleth authentication. See more discussion on this here: :doc:`shibboleth`.) | ||
|
||
|
||
The script will prompt you for some configuration values. If this is a test/evaluation installation, it may be possible to accept the default values provided for most of the settings: |
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.
@landreev doesn't the script prompt for more things now? System email? Solr? Other stuff? If so, we should add them below, right?
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.
I addressed this in 60a9b35
I just tested |
- Keep the list of default values up to date. - Consistent capitalization of PostgreSQL and Solr.
@landreev and @kcondon I'm done messing with docs in this branch. Here's what I changed: b59295f Installation Guide: fix typo #2944 60a9b35 is about keeping the list of questions and default values the installer asks about up to date. I think people might appreciate seeing this in the docs before running the installer. Dunno. I hope so. :) |
Removed section about fixing the admin email account since the installer now requires this.
Go ahead and merge. |
RFI Checklist
Before submitting the pull request, fill out sections (1.) Related Issues and (2.) Pull Request Checklist.
1. Related Issues
List and link to the issues in this Pull Request.
#3016
#2980
#2311
#1455
#1201
#1167
#1097
2. Pull Request Checklist
3. Review Checklist
After the pull request has been submitted, fill out this section.