Skip to content
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

Merged
merged 22 commits into from
Mar 17, 2016
Merged

4.3 installer improvements #3017

merged 22 commits into from
Mar 17, 2016

Conversation

landreev
Copy link
Contributor

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

  • [#### + Title HERE]

2. Pull Request Checklist

  • Functionality completed as described in FRD (N/A)
  • Dependencies, risks, assumptions in FRD addressed (N/A)
  • Unit tests completed (N/A)
  • Deployment requirements identified (e.g., SQL scripts, indexing)
  • Documentation completed
  • All code checkins completed

3. Review Checklist

After the pull request has been submitted, fill out this section.

  • Code review completed or waived
  • Testing requirements completed
  • Usability testing completed or waived - waived
  • Support testing completed or waived - waived
  • Merged with develop branch and resolved conflicts

@@ -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!
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! At some point I should reconfigure Vagrant to run the installer as non-root now that this is supported. #1934 and #2443 are highly related to the fact that previously the installer had to be run as root.

(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:
Copy link
Member

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?

Copy link
Member

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

@pdurbin
Copy link
Member

pdurbin commented Mar 16, 2016

I just tested vagrant up on 1a3b2dd and it works fine (I can log in). Here's the output: vagrant-up-1a3b2dd.txt

- Keep the list of default values up to date.
- Consistent capitalization of PostgreSQL and Solr.
@pdurbin
Copy link
Member

pdurbin commented Mar 16, 2016

@landreev and @kcondon I'm done messing with docs in this branch. Here's what I changed:

b59295f Installation Guide: fix typo #2944
49217a0 Solr: explain requestHeaderSize better #2311
0553437 Installer: typo #3016
60a9b35 Installer: minor doc improvements #3016

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.
@kcondon
Copy link
Contributor

kcondon commented Mar 17, 2016

Go ahead and merge.

scolapasta added a commit that referenced this pull request Mar 17, 2016
@scolapasta scolapasta merged commit b39c957 into develop Mar 17, 2016
@pdurbin pdurbin deleted the 4.3-installer-improvements branch April 28, 2016 19:47
@scolapasta scolapasta added this to the 4.3 milestone May 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants