X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/46b11ba2ed71e2c074e9e6c8f5b9f7a003e7067f..0eb72b526bf8bbb011551ecf019f604e17a534f1:/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 695584fa24..7201460dde 100644 --- a/doc/install/install-api-server.html.textile.liquid +++ b/doc/install/install-api-server.html.textile.liquid @@ -3,6 +3,11 @@ layout: default navsection: installguide title: Install the API server ... +{% comment %} +Copyright (C) The Arvados Authors. All rights reserved. + +SPDX-License-Identifier: CC-BY-SA-3.0 +{% endcomment %} h2. Install prerequisites @@ -12,10 +17,6 @@ h3(#install_ruby_and_bundler). Install Ruby and Bundler {% include 'install_ruby_and_bundler' %} -h3(#install_postgres). Install PostgreSQL - -{% include 'install_postgres' %} - h2(#install_apiserver). Install API server and dependencies On a Debian-based system, install the following packages: @@ -34,57 +35,17 @@ On a Red Hat-based system, install the following packages: {% include 'install_git' %} -h2. Set up the database - -Generate a new database password. Nobody ever needs to memorize it or type it, so we'll make a strong one: +h2(#configure). Set up the database - -
~$ ruby -e 'puts rand(2**128).to_s(36)'
-6gqa1vu492idd7yca9tfandj3
-
- -Create a new database user. +Configure the API server to connect to your database by updating @/etc/arvados/api/database.yml@. Replace the @xxxxxxxx@ database password placeholder with the "password you generated during database setup":install-postgresql.html#api. Be sure to update the @production@ section. -
~$ sudo -u postgres createuser --encrypted -R -S --pwprompt arvados
-[sudo] password for you: yourpassword
-Enter password for new role: paste-password-you-generated
-Enter it again: paste-password-again
+
~$ editor /etc/arvados/api/database.yml
 
-{% 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' %} - -Create the database: - - -
~$ sudo -u postgres createdb arvados_production -T template0 -E UTF8 -O arvados
-
-
- -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. @@ -197,43 +158,15 @@ Example @application.yml@:
-h2(#set_up). Set up Web servers - -For best performance, we recommend you use Nginx as your Web server front-end, with a Passenger backend for the main API server and a Puma backend for API server Websockets. To do that: - - -
    -
  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:

    - -
    #!/bin/bash
    -
    -set -e
    -exec 2>&1
    -
    -# Uncomment the line below if you're using RVM.
    -#source /etc/profile.d/rvm.sh
    +h2(#set_up). Set up Nginx and Passenger
     
    -envdir="`pwd`/env"
    -mkdir -p "$envdir"
    -echo ws-only > "$envdir/ARVADOS_WEBSOCKETS"
    +The Nginx server will serve API requests using Passenger. It will also be used to proxy SSL requests to other services which are covered later in this guide.
     
    -cd /var/www/arvados-api/current
    -echo "Starting puma in `pwd`"
    +First, "Install Nginx and Phusion Passenger":https://www.phusionpassenger.com/library/walkthroughs/deploy/ruby/ownserver/nginx/oss/install_passenger_main.html.
     
    -# Change arguments below to match your deployment, "webserver-user" and
    -# "webserver-group" should be changed to the user and group of the web server
    -# process.  This is typically "www-data:www-data" on Debian systems by default,
    -# other systems may use different defaults such the name of the web server
    -# software (for example, "nginx:nginx").
    -exec chpst -m 1073741824 -u webserver-user:webserver-group -e "$envdir" \
    -  bundle exec puma -t 0:512 -e production -b tcp://127.0.0.1:8100
    -
    -
  4. - -
  5. Edit the http section of your Nginx configuration to run the Passenger server, and act as a front-end for both it and Puma. You might add a block like the following, adding SSL and logging parameters to taste:

    +Edit the http section of your Nginx configuration to run the Passenger server, and serve SSL requests. Add a block like the following, adding SSL and logging parameters to taste: +
    server {
       listen 127.0.0.1:8000;
       server_name localhost-api;
    @@ -244,17 +177,20 @@ exec chpst -m 1073741824 -u webserver-user:webserver-group -e "$envdir" \
       passenger_enabled on;
       # If you're using RVM, uncomment the line below.
       #passenger_ruby /usr/local/rvm/wrappers/default/ruby;
    +
    +  # This value effectively limits the size of API objects users can
    +  # create, especially collections.  If you change this, you should
    +  # also ensure the following settings match it:
    +  # * `client_max_body_size` in the server section below
    +  # * `client_max_body_size` in the Workbench Nginx configuration (twice)
    +  # * `max_request_size` in the API server's application.yml file
    +  client_max_body_size 128m;
     }
     
     upstream api {
       server     127.0.0.1:8000  fail_timeout=10s;
     }
     
    -upstream websockets {
    -  # The address below must match the one specified in puma's -b option.
    -  server     127.0.0.1:8100  fail_timeout=10s;
    -}
    -
     proxy_http_version 1.1;
     
     # When Keep clients request a list of Keep services from the API server, the
    @@ -277,10 +213,7 @@ server {
     
       index  index.html index.htm index.php;
     
    -  # This value effectively limits the size of API objects users can create,
    -  # especially collections.  If you change this, you should also set
    -  # `max_request_size` in the API server's application.yml file to the same
    -  # value.
    +  # Refer to the comment about this setting in the server section above.
       client_max_body_size 128m;
     
       location / {
    @@ -296,53 +229,26 @@ server {
         proxy_set_header      X-Forwarded-For $proxy_add_x_forwarded_for;
       }
     }
    -
    -server {
    -  listen       [your public IP address]:443 ssl;
    -  server_name  ws.uuid_prefix.your.domain;
    -
    -  ssl on;
    -  ssl_certificate     /YOUR/PATH/TO/cert.pem;
    -  ssl_certificate_key /YOUR/PATH/TO/cert.key;
    -
    -  index  index.html index.htm index.php;
    -
    -  location / {
    -    proxy_pass            http://websockets;
    -    proxy_redirect        off;
    -    proxy_connect_timeout 90s;
    -    proxy_read_timeout    300s;
    -
    -    proxy_set_header      Upgrade $http_upgrade;
    -    proxy_set_header      Connection "upgrade";
    -    proxy_set_header      Host $host;
    -    proxy_set_header      X-Real-IP $remote_addr;
    -    proxy_set_header      X-Forwarded-For $proxy_add_x_forwarded_for;
    -  }
    -}
     
    -
  6. + -
  7. Restart Nginx:

    +Restart Nginx to apply the new configuration. +
    ~$ sudo nginx -s reload
     
    - -
  8. - -
h2. Prepare the API server deployment -Now that all your configuration is in place, run @/usr/local/bin/arvados-api-server-upgrade.sh@. This will install and check your configuration, install necessary gems, and run any necessary database setup. +{% assign railspkg = "arvados-api-server" %} +{% include 'install_rails_reconfigure' %} {% include 'notebox_begin' %} -You can safely ignore the following messages if they appear while this script runs: -
Don't run Bundler as root. Bundler can ask for sudo if it is needed, and installing your bundle as root will
-break this application for all non-root users on this machine.
-
fatal: Not a git repository (or any of the parent directories): .git
-{% include 'notebox_end' %} +You can safely ignore the following messages if they appear while this command runs: -This command aborts when it encounters an error. It's safe to rerun multiple times, so if there's a problem with your configuration, you can fix that and try again. +
Don't run Bundler as root. Bundler can ask for sudo if it is needed, and installing your bundle as root will
+break this application for all non-root users on this machine.
+
fatal: Not a git repository (or any of the parent directories): .git
+{% include 'notebox_end' %}