Before you begin installation

This guide is a supplement to the installation script (see installation folder), which is the newest resource for installing OS2Display.

This document has not been updated as recently as the installation scripts, so problems might occur if you follow this guide. Please make pull requests if you have any errors or issues with the guide, so it can be updated for the next user.

Requirements

The guide assumes that you have an installed linux based server with the following packages installed and at least the versions given.

nginx 1.4.x
redis 2.8.x
php 5.6.x
node 6.x
elastic search 1.7.x
supervisor 3.x
Valid SSL certificates for you domain.

The document also assumes that you are logged in as the user deploy, if this is not the case, you need to change this (e.g. the supervisor run script).

The parts

The system consists of four parts:

Admin - administration interface (symfony)

Screen - that serves content on the screens

Middleware - that handles web-sockets and connection between the ones above.

Search node - that interfaces with elastic search and provide fast content search in the administration interface.

The setup

The middleware and search node is only installed once on each server and then all administration interfaces and screens communicates with the them using API keys to identify them self and ensure content separation.

Conventions

This document uses [] square brackets around the different variables in the configuration templates that needs to be exchanged with the actual values from other parts of the configuration (e.g. API keys).

Her is an explanation of the different key configuration variables.

[server name]
[client name]
[SSL CERT]
[SSL KEY]
[CHANGE ME]
[PASSWORD]
[DB NAME]
[DB USER]
[DB PASSWORD]
[ZENCODER API KEY]
[SHARING API KEY]
[SEARCH API KEY]
[SEARCH INDEX KEY]
[MIDDLEWARE API KEY]
@TODO Document placeholders [...]

Things in boxes are commands that should be executed or configuration thats need in the files given.

Naming

We have chosen to use the following naming convention and place the application in /home/www/.

We have used the following naming in DNS:

search-[server name].aroskanalen.dk
middleware-[server name].aroskanalen.dk
screen-[client name].aroskanalen.dk
admin-[client name].aroskanalen.dk

And this will give the folders:

/home/www/[client name]_aroskanalen_dk/admin
/home/www/[client name]_aroskanalen_dk/screen
/home/www/[client name]_aroskanalen_dk/logs

The Middleware and search node is located in:

/home/www/middleware
/home/www/search_node

Installation

If you already have a running middleware and search node on the server you can skip the steps and just add the needed api-keys in both and add mappings in the search node. You can use the UI or edit the JSON files directly.

Note: To install the newest version (development version that's not aways stable), you should checkout the development branches in the all the cloned repositories instead of the latest version tag.

SSL Configuration

Common SSL-configuration defined in includes/ssl_aroskanalen.conf:

  ssl_certificate /etc/nginx/ssl/[SSL CERT].crt;
  ssl_certificate_key /etc/nginx/ssl/[SSL KEY].key;

  # This should be identicial for all vhosts (nginx < 1.9.6)
  ssl_session_timeout 5m;
  ssl_session_cache shared:SSL:10m;

  # See https://hynek.me/articles/hardening-your-web-servers-ssl-ciphers/
  ssl_prefer_server_ciphers On;
  ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
  ssl_ciphers ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:ECDH+3DES:DH+3DES:RSA+AESGCM:RSA+AES:RSA+3DES:!aNULL:!MD5:!DSS;

Middleware

Clone

Start by cloning the git repository for the middleware and checkout the latest release tag (which can be found using git tag).

cd /home/www
git clone git@github.com:aroskanalen/middleware.git
cd middleware
git checkout [v3.x.x]

Node packages

The middleware is build as a NodeJS application and the different plugins require libraries to be installed. The application comes with an installation script that do this, just run it.

./install.sh

Configuration

First we need to configure nginx in front of the middleware so it's accessible through normal web-ports and also to proxy web-socket connections.

sudo nano -w /etc/nginx/sites-available/nodejs

In this file add an upstream connection to the middleware application. Later a connection for the search node will also added as well.

upstream nodejs_middleware {
  server 127.0.0.1:3020;
}

To access the middleware administration and allow the screen to communication with the middleware a virtual host configuration is needed. You need to change the [server name] with the actual name of the server.

sudo nano -w /etc/nginx/sites-available/middleware_[server name]_aroskanalen_dk

server {
  listen 80;

  server_name middleware-[server name].aroskanalen.dk;
  rewrite ^ https://$server_name$request_uri? permanent;

  access_log /var/log/nginx/middleware_access.log;
  error_log /var/log/nginx/middleware_error.log;
}

# HTTPS server
#
server {
  listen 443 ssl;

  server_name middleware-[server name].aroskanalen.dk;

  include /etc/nginx/includes/ssl_aroskanalen.conf;

  access_log /var/log/nginx/middleware_access.log;
  error_log /var/log/nginx/middleware_error.log;

  location / {
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header Host $http_host;

    proxy_buffering off;

    proxy_pass http://nodejs_middleware/;
    proxy_redirect off;
  }

  location /socket.io/ {
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";

    proxy_pass http://nodejs_middleware;
  }
}

Next step is to configure the application by setting the secret (used to encode security tokens use to ensure safe communication with the middleware) and administrator users password. If you have other applications on the server that's using Redis, you can change the default database using the "db" key under cache section in the configuration file (by default redis has the database 1 to 15 available).

nano -w /home/www/middleware/config.json

{
  "port": 3020,
  "secret": "[CHANGE ME]",
  "log": {
    "file": "messages.log",
    "debug": false
  },
  "admin": {
    "username": "admin",
    "password": "[PASSWORD]"
  },
  "cache": {
    "port": "6379",
    "host": "localhost",
    "auth": null,
    "db": 1
  },
  "apikeys": "apikeys.json"
}

Before starting and testing the middleware application you need to create the apikeys.json file with an empty JSON object or optionally added the demo key below. If you only add an empty ({}) JSON object you need to use the middleware UI through a web-browser to add API keys. It will help you generate random keys.

Note: Each installation of the administration interface (Symfony backend) and screens requires a new API key to ensure separation of data in the middleware. The middleware UI also provides a status page to reload and logout screen and see if the screens are connected to the middleware.

nano -w /home/www/middleware/apikeys.json

Demo content for the apikeys.json file. This API key should not be used in production environments as the key is public known.

{
  "03303f8bf868b517bb732326aca86714": {
    "name": "[client name]",
    "expire": 300,
    "backend": "https://admin-[client name].aroskanalen.dk"
  }
}

Enable nginx configuration by adding symbolic links into the sites-enabled folder and restarting the service.

cd /etc/nginx/sites-enabled/
sudo ln -s ../sites-available/middleware_[server name]_aroskanalen_dk
sudo ln -s ../sites-available/nodejs
sudo service nginx restart

The middleware needs to be started at boot time which requires a Supervisor run script. Supervisor will also ensure that the node application is started again, if an error happens and it stops running.

sudo nano -w /etc/supervisor/conf.d/middleware.conf

The run script to keep the middleware running.

[program:middleware]
command=/usr/bin/node /home/www/middleware/app.js
autostart=true
autorestart=true
environment=NODE_ENV=production
stderr_logfile=/var/log/middleware.err.log
stdout_logfile=/var/log/middleware.out.log
user=deploy

Now restart the supervisor service to get the middleware running.

sudo service supervisor restart

UI

@TODO: How to use the UI to add more configuration ap-keys.

Search node

The search node application is a general purpose application to provide a fast search engine through web-socket connections (using elasticsearch) and is designed to be used by other projects as well as aroskanalen. As a result of this, it will not follow the same versioning as the other parts of this installation. It's also why its UI is somewhat complex to use when setting up the right mappings to be used with aroskanalen.

Clone

Start by cloning the git repository for the search node and checkout the latest release tag (which can be found using git tag).

cd /home/www
git clone git@github.com:aroskanalen/search_node.git
cd search_node
git checkout [v1.x.x]

Node packages

Search node, as the middleware, uses a plugin architecture that requires installation of libraries from the node package manager (npm). The application comes with an installation script to handle this, simply go to the root of the application and execute the script.

cd /home/www/search_node/
./install.sh

Configuration

We need to configure nginx to sit in front of the search node so it is accessible through normal web-ports and also proxy web-socket connections. So we add the upstream connection configuration in the nodejs configuration file used by the middleware.

sudo nano -w /etc/nginx/sites-available/nodejs

Append this upstream connection definition to the file.

upstream nodejs_search {
  server 127.0.0.1:3010;
}

To access the search node UI and allow the aroskanalen administration interface to communication with the search node a virtual host configuration is needed. You need to change the [server name] with the actual name of the server.

sudo nano -w /etc/nginx/sites-available/search_[server name]_aroskanalen_dk

server {
  listen 80;

  server_name search-[server name].aroskanalen.dk;
  rewrite ^ https://$server_name$request_uri? permanent;

  access_log /var/log/nginx/search_access.log;
  error_log /var/log/nginx/search_error.log;
}

# HTTPS server
#
server {
  listen 443 ssl;

  server_name search-[server name].aroskanalen.dk;

  include /etc/nginx/includes/ssl_aroskanalen.conf;

  access_log /var/log/nginx/search_access.log;
  error_log /var/log/nginx/search_error.log;

  location / {
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header Host $http_host;

    proxy_buffering off;

    proxy_pass http://nodejs_search/;
    proxy_redirect off;
  }

  location /socket.io/ {
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";

    proxy_pass http://nodejs_search;
  }
}

Enable the configuration by adding a symbolic links for the search node. The nodejs configuration file should be linked during configuration of the middleware. Restart nginx to enable the configuration.

cd /etc/nginx/sites-enabled/
sudo ln -s ../sites-available/search_[server name]_aroskanalen_dk
sudo service nginx restart

Next the application needs to be configured by adding the following content to config.json. Remember to update the administration password and secret.

sudo nano -w /home/www/search_node/config.json

{
  "port": 3010,
  "secret": "[CHANGE ME]",
  "admin": {
    "username": "admin",
    "password": "[PASSWORD]"
  },
  "log": {
    "file": "messages.log",
    "debug": false
  },
  "search": {
    "hosts": [ "localhost:9200" ],
    "mappings": "mappings.json"
  },
  "apikeys": "apikeys.json"
}

Before the application can be started the apikeys.json and mappings.json needs to exist and at least contain an empty JSON object ({}).

echo '{}' > /home/www/search_node/apikeys.json
echo '{}' > /home/www/search_node/mappings.json

The search node needs to be started at boot time which requires a Supervisor run script. Supervisor will also ensure that the node application is restarted, if an error happens and it stops unexpectedly.

sudo nano -w /etc/supervisor/conf.d/search_node.conf

Supervisor run script for the search node.

[program:search-node]
command=node /home/www/search_node/app.js
autostart=true
autorestart=true
environment=NODE_ENV=production
stderr_logfile=/var/log/search-node.err.log
stdout_logfile=/var/log/search-node.out.log
user=deploy

sudo service supervisor restart

As mentioned the search node is not specially created for aroskanalen, so the mappings (configuration for elasticsearch) can be somewhat complex to setup in the UI. To get you started the mapping below can be used as a template for the configuration.

As we need the UI to complete the setup correctly the node application needs to have write access to the files.

cd /home/www/search_node/
chmod +w apikeys.json mappings.json

Now use the UI (https://search-[server name].aroskanalen.dk) and add a new api key. Then go to the mappings tabs in the UI and add a new empty mapping. Next edit the mappings file and add the fields, tag and dates section as in the template. This way you will get a new API key and search index key for each installation. _Note that each installation of the admin application requires a new API key and search index.

nano -w /home/www/search_node/mappings.json

{
  "5d437a016271077510c640e450bde9c3": {
    "name": "demo",
    "tag": "private",
    "fields": [
      {
        "field": "title",
        "type": "string",
        "language": "da",
        "country": "DK",
        "default_analyzer": "string_index",
        "sort": true,
        "indexable": true
      },
      {
        "field": "name",
        "type": "string",
        "language": "da",
        "country": "DK",
        "default_analyzer": "string_index",
        "sort": true,
        "indexable": true
      }
    ],
    "dates": [
      "created_at",
      "updated_at"
    ]
  }
}

Activating the search index

When you have update the mappings file go back into the UI and select the indexes that you need by edit the API key and select it/them in the edit window. Before a given index can be used you need to activate it in the indexes tab. So do that now.

UI

@TODO: How to use the UI to add more configuration.

Administration User Interface

The administration user interface is the backend of the display system and used to add content and setup screens etc.

Clone

cd /home/www/[client name]_aroskanalen_dk
git clone git@github.com:aroskanalen/admin.git

It needs to have an SQL database and in this guide we assumes that it's MySQL or MariaDB, so start by creating a database and user given the user privileges to use the database.

mysql -u root -p -e "CREATE DATABASE [DB NAME];"
mysql -u root -p -e "CREATE USER '[DB USER]'@'localhost' IDENTIFIED BY '[DB PASSWORD]';"
mysql -u root -p -e "GRANT ALL PRIVILEGES ON [DB NAME].* TO '[DB USER]'@'localhost';"
mysql -u root -p -e "FLUSH PRIVILEGES;"

Install the site using composer.

cd /home/www/[client name]_aroskanalen_dk/admin
composer install

Fill out the questions that you can and use default values for the rest. We will come back to the values below. See the parameters example below to help filling out the values. If you are interested in Symfony you can see their default installation manual at http://symfony.com/doc/current/book/installation.html.

If you want to be able to upload videos to the system you need to have a zencoder account at http://zencoder.com/, which is an online video conversion service. When you upload an video to the system, it sends it to zencoder that re-encodes the video to the formats supported by browser. It's a payed service an is optional, if you don't want videos just write NULL as value.

The koba (Kalender Og Booking Applikation) is a project under Aarhus Kommmune that allows us to display Exchange location bookings on screens. But as this as somewhat a highly specialised service/API you may not have access to it. If not simply use NULL as API key value.

In relation to the sharing section of the configuration it's used to share content across different installations by using a shared API key and index in the search node. The index requires to have the same configuration as a normal index or the aroskanalen, but with a "tag" set to "shared".

The final app/config/parameters.yml file.

parameters:
    database_driver: pdo_mysql
    database_host: 127.0.0.1
    database_port: null
    database_name: [DB NAME]
    database_user: [DB USER]
    database_password: '[DB PASSWORD]'

    mailer_transport: sendmail
    mailer_host: 127.0.0.1
    mailer_user: null
    mailer_password: null
    mailer_from_email: webmaster@ik3.aroskanalen.vm
    mailer_from_name: 'Webmaster Aroskanalen'

    locale: en
    secret: [CHANGE ME]
    debug_toolbar: false
    debug_redirects: false
    use_assetic_controller: true

    absolute_path_to_server: 'https://admin-[client name].aroskanalen.dk'
    zencoder_api: [ZENCODER API KEY]

    sharing_host: 'https://search-[server name].aroskanalen.dk'
    sharing_path: /api
    sharing_apikey: [SHARING API KEY]
    sharing_enabled: false

    search_host: 'https://search-[server name].aroskanalen.dk'
    search_path: /api
    search_apikey: [SEARCH API KEY]
    search_index: [SEARCH INDEX KEY]

    middleware_host: 'https://middleware-[server name].aroskanalen.dk'
    middleware_path: /api
    middleware_apikey: [MIDDLEWARE API KEY]

    site_title: 'Demo Aroskanalen'

    koba_apikey: [KOBA API KEY]
    koba_path: 'http://koba.aarhus.dk'

    version: [RELEASE_VERSION]

    itk_log_version: 1
    itk_log_error_callback: /api/error
    itk_log_log_to_console: false
    itk_log_log_level: all

The web-server needs access to different locations in the filesystem, so you need to change the owner of the folders to the nginx user.

cd /home/www/[client name]_aroskanalen_dk/admin
sudo chown -R www-data app/cache/ app/logs/ web/uploads/

You can check you site configuration by running this command.

cd /home/www/[client name]_aroskanalen_dk/admin
php app/check.php

Now install the database tables by running the database update command.

php app/console doctrine:schema:update --force

Add an administrator user that can be used to test the site and create other users.

php app/console fos:user:create [admin username] [test@example.com] [password] --super-admin

Templates

Templates reside in the /web/templates folder. They are separated into screen and slide templates. Each template has its own folder and .json file that needs to be imported into the database. This steps also needs to be executed every time templates are updated or new templates are added to the installation.

cd /home/www/[client name]_aroskanalen_dk/admin
php app/console ik:templates:load

In the administration menu there is a menu option to enable/disable imported templates.

Cron

The system uses a cron job to push content from the administration interface to the middleware. To push content every minute edit crontab and add the line below, it will one push new content and updates.

crontab -e

Add this to crontab.

*/1 * * * * /usr/bin/php /home/www/[client name]_aroskanalen_dk/admin/app/console ik:cron > /dev/null 2>&1

For production sites add --env=prod:

*/1 * * * * /usr/bin/php /home/www/[client name]_aroskanalen_dk/admin/app/console --env=prod ik:cron > /dev/null 2>&1

Note: Adding --env=prod may result in permissions issues, but you can fix this by settings up the crontab for the right user, e.g. www-data:

sudo crontab -u www-data -e

Zencoder

To encode videos Job queue bundle is used that requires supervisor script be executed.

nano -w /etc/supervisor/conf.d/job_queue.conf

[program:jms_job_queue_runner]
command=/usr/bin/php /home/www/backend/app/console jms-job-queue:run --verbose
numprocs=1
directory=/tmp
autostart=true
autorestart=true
startsecs=5
startretries=10
user=www-data
redirect_stderr=false
stderr_logfile=/var/log/job-queue.err.log
stdout_logfile=/var/log/job-queue.out.log
stdout_capture_maxbytes=1MB
stderr_capture_maxbytes=1MB

Nginx configuration

As with the node applications the administration interface needs a nginx configuration to be accessible from the network.

sudo nano -w /etc/nginx/sites-available/admin_[client name]_aroskanalen_dk

You need to update the name, paths and ssl certificates.

server {
  listen 80;
  server_name admin-[client name].aroskanalen.dk;

  rewrite ^ https://$server_name$request_uri? permanent;

  access_log /home/www/[client name]_aroskanalen_dk/logs/backend_access.log;
  error_log /home/www/[client name]_aroskanalen_dk/logs/backend_error.log;
}

# HTTPS server
#
server {
  listen 443 ssl;

  server_name admin-[client name].aroskanalen.dk;

  include /etc/nginx/includes/ssl_aroskanalen.conf;

  root /home/www/[client name]_aroskanalen_dk/admin/web;

  client_max_body_size 300m;

  access_log /home/www/[client name]_aroskanalen_dk/logs/backend_access.log;
  error_log /home/www/[client name]_aroskanalen_dk/logs/backend_error.log;

  location / {
    # try to serve file directly, fallback to rewrite
    try_files $uri @rewriteapp;
  }

  location /templates/ {
    add_header 'Access-Control-Allow-Origin' "*";
  }

  location @rewriteapp {
    # rewrite all to app.php
    rewrite ^(.*)$ /app.php/$1 last;
  }

  location ~ ^/(app|app_dev|config)\.php(/|$) {
    fastcgi_pass unix:/var/run/php5-fpm.sock;
    fastcgi_split_path_info ^(.+\.php)(/.*)$;
    include fastcgi_params;
    fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
    fastcgi_param HTTPS off;
  }

  # deny access to .htaccess files, if Apache's document root
  # concurs with nginx's one
  location ~ /\.ht {
    deny all;
  }

  location /proxy/ {
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header Host $http_host;

    proxy_buffering off;

    proxy_pass http://nodejs_search/;
    proxy_redirect off;
  }

  location /socket.io/ {
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";

    proxy_pass http://nodejs_search;
  }
}

Enable the configuration by adding a symbolic link for the configuration and restart nginx to enable it.

cd /etc/nginx/sites-enabled/
sudo ln -s ../sites-available/admin_[client name]_aroskanalen_dk
sudo service nginx restart

Login to the site and create a new screen, channel and slide to test that it works, you will get a search error until there is something in the search indexes for each of the content types. Also try to upload media, such as an image to test file permissions.

Screens

Screens are the part of the system used to display the content on, well screens. It communicates via web-socket with the middleware and fetches images and templates form its backend.

Clone

First clone the screen code.

 cd /home/www/[client name]_aroskanalen_dk
 git clone git@github.com:aroskanalen/screen.git

Edit the configuration file in app/config.js and use the template below to fill out the configuration. Note that this is not a JSON file but a javascript (.js) file.

 cd /home/www/[client name]/screen
 nano app/config.js

window.config = {
  "resource": {
    "server": "//screen-[client name].aroskanalen.dk/",
    "uri": "proxy"
  },
  "ws": {
    "server": "https://screen-[client name].aroskanalen.dk/"
  },
  "backend": {
    "address": "https://admin-[client name].aroskanalen.dk/"
  },
  "apikey": "[MIDDLEWARE API KEY]",
  "cookie": {
    "secure": false
  },
  "debug": true,
  "version": "[RELEASE_VERSION]",
  "itkLog": {
    "version": "1",
    "errorCallback": "https://admin-[client name].aroskanalen.dk/api/error",
    "logToConsole": false,
    "logLevel": "error"
  },
  "fallback_image": null
};

The screen application also needs to be configured to run in nginx.

sudo nano -w /etc/nginx/sites-available/screen_[client name]_aroskanalen_dk

server {
  listen 80;

  server_name screen-[client name].aroskanalen.dk;

  rewrite ^ https://$server_name$request_uri? permanent;

  access_log /home/www/[client name]_aroskanalen_dk/logs/screen_access.log;
  error_log /home/www/[client name]_aroskanalen_dk/logs/screen_error.log;
}

# HTTPS server
#
server {
  listen 443 ssl;

  server_name screen-[client name].aroskanalen.dk;

  include /etc/nginx/includes/ssl_aroskanalen.conf;

  root /home/www/[client name]_aroskanalen_dk/screen;

  access_log /home/www/[client name]_aroskanalen_dk/logs/screen_access.log;
  error_log /home/www/[client name]_aroskanalen_dk/logs/screen_error.log;

  location / {
    try_files $uri $uri/ /index.html;
  }

  location /templates/ {
    add_header 'Access-Control-Allow-Origin' "*";
  }

  location /proxy/ {
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header Host $http_host;

    proxy_buffering off;

    proxy_pass http://nodejs_middleware/;
    proxy_redirect off;
  }

  location /socket.io/ {
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";

    proxy_pass http://nodejs_middleware;
  }
}

Enable the configuration by adding a symbolic link for the installation and restart nginx to enable the configuration.

cd /etc/nginx/sites-enabled/
sudo ln -s ../sites-available/screen_[client name]_aroskanalen_dk
sudo service nginx restart

Troubleshooting

nginx -t can be used to test configuration file.
ps -ef | grep node to see if the node applications are running (middleware and search node)
node app.js can be used to run the middleware and search node manual to see if they throw an errors, which may give an hit to whats wronge.

Note that the supervisor have to be stop first our the communication port is already in use (an gives an error).

php app/console ik:push --force can be used to force push content from the administration interface to the middleware.
You can logout of a screen by pressing ctrl+l at any time.
If indexes are defined, but the index list is empty, you may have to restart the "elasticsearch" and "redis-server services"

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Installation guide.md

Installation guide.md

Before you begin installation

Requirements

The parts

The setup

Conventions

Naming

Installation

SSL Configuration

Middleware

Clone

Node packages

Configuration

UI

Search node

Clone

Node packages

Configuration

Activating the search index

UI

Administration User Interface

Clone

Templates

Cron

Zencoder

Nginx configuration

Screens

Clone

Troubleshooting

Files

Installation guide.md

Latest commit

History

Installation guide.md

File metadata and controls

Before you begin installation

Requirements

The parts

The setup

Conventions

Naming

Installation

SSL Configuration

Middleware

Clone

Node packages

Configuration

UI

Search node

Clone

Node packages

Configuration

Activating the search index

UI

Administration User Interface

Clone

Templates

Cron

Zencoder

Nginx configuration

Screens

Clone

Troubleshooting