-
Notifications
You must be signed in to change notification settings - Fork 486
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
Install script with application and prostgres on different servers not taking PGPASSWORD #5644
Comments
@joseagaleano thanks for reporting this issue! I just assigned it to you since you mentioned you're going to work on it at https://groups.google.com/d/msg/dataverse-community/o91IaORh2V0/7Pc1DP6sBAAJ As I mentioned in that thread, Harvard Dataverse used to have PostgreSQL on a separate server. The architecture looked something like this: (That image is from http://guides.dataverse.org/en/4.11/installation/prep.html#advanced-installation ) These days Harvard Dataverse uses Amazon RDS for PostgreSQL instead. I'm not sure how many other installations of Dataverse run PostgreSQL on a separate server but hopefully some of them are out there and can offer some advice. |
@joseagaleano hi! I just thought I'd check if you're blocked. Do you need any help with this? |
@joseagaleanoc hi! Are you still working on this issue? I wanted to let you know that there is a plan to rewrite that |
The rewrite was done in this PR: @joseagaleanoc are you still interested in this issue you opened? Thanks. |
Trying to install Dataverse on AWS services and have one server for the application and another for the Databsae. Both the ADMIN and the Dataverse Postgres User have different passwords.
I get the following error executing ./install:
I understand its a connection error. I modified install and included on the command to include -W
This works but it prompts for the ADMIN password, but the rest of the queries fail. Again if I set the -W parameter on the following queries it works but I have input the ADMIN password (which is like 5 times)
The text was updated successfully, but these errors were encountered: