X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/ef3e45fcc338a85432c207685567385972f79ee6..aec99288fab5ceed8dc746e62efaeee33ff38a82:/doc/install/install-api-server.html.textile.liquid diff --git a/doc/install/install-api-server.html.textile.liquid b/doc/install/install-api-server.html.textile.liquid index fae06decb8..91e2c69892 100644 --- a/doc/install/install-api-server.html.textile.liquid +++ b/doc/install/install-api-server.html.textile.liquid @@ -52,11 +52,9 @@ Enter password for new role: paste-password-you-generate Enter it again: paste-password-again -{% include 'notebox_begin' %} - -This user setup assumes that your PostgreSQL is configured to accept password authentication. Red Hat systems use ident-based authentication by default. You may need to either adapt the user creation, or reconfigure PostgreSQL (in @pg_hba.conf@) to accept password authentication. - -{% include 'notebox_end' %} +{% assign pg_hba_path = "/opt/rh/postgresql92/root/var/lib/pgsql/data/pg_hba.conf" %} +{% assign pg_service = "postgresql92-postgresql" %} +{% include 'install_redhat_postgres_auth' %} Create the database: @@ -65,26 +63,13 @@ Create the database: -h2. Set up configuration files - -The API server package uses configuration files that you write to @/etc/arvados/api@ and ensures they're consistently deployed. Create this directory and copy the example configuration files to it: - - -
~$ sudo mkdir -p /etc/arvados/api
-~$ sudo chmod 700 /etc/arvados/api
-~$ cd /var/www/arvados-api/current
-/var/www/arvados-api/current$ sudo cp config/database.yml.example /etc/arvados/api/database.yml
-/var/www/arvados-api/current$ sudo cp config/application.yml.example /etc/arvados/api/application.yml
-
-
- h2. Configure the database connection Edit @/etc/arvados/api/database.yml@ and replace the @xxxxxxxx@ database password placeholders with the PostgreSQL password you generated above. h2(#configure_application). Configure the API server -Edit @/etc/arvados/api/application.yml@ to configure the settings described in the following sections. The deployment script will consistently deploy this to the API server's configuration directory. The API server reads both @application.yml@ and its own @config/application.default.yml@ file. The settings in @application.yml@ take precedence over the defaults that are defined in @config/application.default.yml@. The @config/application.yml.example@ file is not read by the API server and is provided as a starting template only. +Edit @/etc/arvados/api/application.yml@ to configure the settings described in the following sections. The API server reads both @application.yml@ and its own @config/application.default.yml@ file. The settings in @application.yml@ take precedence over the defaults that are defined in @config/application.default.yml@. The @config/application.yml.example@ file is not read by the API server and is provided as a starting template only. @config/application.default.yml@ documents additional configuration settings not listed here. You can "view the current source version":https://dev.arvados.org/projects/arvados/repository/revisions/master/entry/services/api/config/application.default.yml for reference. @@ -205,7 +190,9 @@ For best performance, we recommend you use Nginx as your Web server front-end, w
  1. Install Nginx and Phusion Passenger.
  2. -
  3. Puma is already included with the API server's gems. We recommend you run it as a service under runit or a similar tool. Here's a sample runit script for that:

    +
  4. Install runit to supervise the Puma daemon. {% include 'install_runit' %}

  5. + +
  6. Install the script below as the run script for the Puma service, modifying it as directed by the comments.

    #!/bin/bash