Installation Guide

Installation

Due to the variations of environments, we need to break out the installation guide into 3 different sections: Dedicated Hosting (VPS), Shared Hosting /w SSH and Composer and Shared Hosting without SSH and Composer.

To understand what section you fall in, Here's a list of scenarios and examples.

Dedicated Hosting - You have direct control over the entire operating system installed on either a virtual machine or a physical machine.

Shared Hosting Overall Definition - This means you don't have direct control over the operating system and software installed and instead are presented with a control panel (cPanel, Webmin, etc) to manage your website. Your hosting account is usually stored in the /home/[account] folder and you have your public_html folder for where your website goes.

Shared Hosting /w SSH and Composer - The above except your hosting company allows for you to make changes and run commands in a Secure SHell method (using PuTTY or macOS Terminal). Composer, a php dependency tool, is also installed on the server to manage php libraries which Laravel uses.

Dedicated Server

Due to the many variations of operating systems you will find floating around in the linux space for dedicated hosting, we will be primarily focussing on Ubuntu 16.04 LTS. This operating system is the one that is being used to power the VAOS master system and FS Hub.

Pre-requisites

Instead of making this guide way longer, Here is a guide to setup a secure hosting environment using nginx, MySQL 5.7, and PHP 7.0; also known as the LEMP stack.

https://goo.gl/urUJFt

What's not listed is how to update to PHP 7.1. That you can find rather easily by using our friend Google.

The full list of requirements are as follows

• MySQL 5.7
• nginx 1.12.1 or Apache 2.4
• PHP 7.0 and up (FPM version for nginx)
• Git for updates
• Composer (either via the .phar file or globally)

Pulling in the VAOS Project From GitHub

With all our pre-requisites in place, it is now time to download the project. First we should decide on a installation directory. /var/www is created when you first install nginx. You can either create a sub directory to host the site in there, or put it in your linux home folder /home/[yournamehere]. Both methods are perfectly valid as long as the permissions are setup properly.

Now, that we have decided, let's pull in the project. First, lets go over the syntax we will be using.

git clone [repository address] [folder name]

So, let's see it in action:

cd /var/www
git clone https://github.com/fsvaos/vaos VAOS

This pulled the project and the latest updates from GitHub into the /var/www/VAOS folder.