Minimal Linux

Installing Bedrock & Wordpress For Theme Development Using An Apache VirtualHost Server On Centos 7 RHEL.

noreply@blogger.com (Paul Anthony McGowan) — Mon, 20 Nov 2017 09:58:00 +0000

Bedrock from Roots is a great tool for developing Wordpress projects and comes with a huge range of functionality including explicit dependency tracking using Composer

This tutorial is to create an installation of Bedrock using an Apache VirtualHost Server setup on a local Linux machine.

Its a self-contained WordPress stack that installs an explicit version of WordPress and required plug-ins (

composer
install

) which can be easily configured. All configuration is kept in a .env text file).

It has a multi-stage environment and you can have a

development

configuration for working locally, a staging configuration for tests, and a production configuration for the live site.

System Requirements

Below are the requirements for working with Bedrock

You should be comfortable working on the command line.

PHP >= 5.5

You need Composer on the server (install instructions)

You need to have a working Ruby and gem environment on your machine to perform deploys.

You need to have WP-CLI installed locally and on the server if you plan to use it. It's not required, but it is a useful tool (install instructions)

This is in addition to all the normal WordPress server requirements, like MySQL etc.

Set Up An Apache VirtualHost Server For Local Development With own Domain Name etc.

First Set Up Your VirtualHost Server by following the tutorial at

https://minimallinux.blogspot.co.uk/2017/11/set-up-virtual-hosts-for-apache-on.html

When you have done this (just create one VirtualHost Server for now, you can create more another time) then you will install bedrock in to the root of that server, which if you have done it correctly should be nicely on your desktop in a folder called vhost1.com or your chosen name. I will use vhost1.com for this tutorial.

Installing Bedrock

For a brand new WordPress project. First, you'll need a copy of Bedrock, which you can get from its repo at

https://github.com/roots/bedrock

Don't clone the repo because you are going to use for for your own changes, and create your own repo for your projects, just download the zip file and extract it in to your vhost1.com folder, then enter the bedrock directory and cut/paste the contents from bedrock master in to the root vhost1.com folder (delete the now unused bedrock master folder)

So you have bedrock installed at the root of your vhost1.com server not in its own folder. You will just have 2 main levels to deal with for now, the root at vhost1.com and the sub folder /web/ with a wordpress installation in it.

Now that you have downloaded the repo and added it to your vhost1.com server, you can initialize your own repository for the project with git initialize in the vhost1.com root.

$ git init

Install Composer dependencies.

Install the Composer dependencies like Wordpress etc, (however I am going to change some of these), Composer puts Wordpress in the /web/ folder of bedrock under a folder called wp.

Change Wordpress version. (optional)

The default version of Wordpress that composer currently installs is the latest version, and I have a bug with it which prevents me changing themes properly which is not much good if you are building a new theme, so I use an older version of Wordpress, typically 4.8, so I change the Wordpress entry in composer.json to 4.8 (from 4.9).

Otherwise if you are happy with 4.9 just run

$ composer install (from root of vhost1.com/bedrock)

(Later on, you can also upgrade Wordpress at any time by running)

$ composer require johnpbloch/wordpress <version no>

(And update the database schema with)

$ wp core update-db

Now create a database for your bedrock/wordpress install.

Create an empty database called bedrock in mysql command or gui program (or your chosen name)

Hit Control + H in vhost1.com root (now bedrock root) to reveal the hidden files, you need to create a .env file to get set up.

Open up .env.example and save it as .env in order to set up the configuration of Bedrock and Wordpress.

Change the values as below

DB_NAME=bedrock (or the database name you created)

DB_USER= your mysql user

DB_PASSWORD=your mysql user password

# Optional variables

# DB_HOST=localhost

# DB_PREFIX=wp_

(You will leave the above 2 values until the Wordpress install, the host refers to the database host not your VirtualHost name, so it will probably be localhost. Enter that and the table prefix if required at the install stage when you browse to it.)

Your wp_home is the web folder inside vhost1.com root and the wp_siteurl is the wp folder inside of that. So as below.

WP_ENV=development

WP_HOME=http://vhost1.com/web/

WP_SITEURL=${WP_HOME}/wp

Generate your keys here: https://roots.io/salts.html and just copy/paste them into the last section.

Save the file and browse to http://vhost1.com/web/wp/ to start the wordpress installation.

Enter the usual details mainly referring to the database and install Wordpress in to your Bedrock project.

You may have to manually create a wp-config.php file which you just copy/paste the given values in to the vhost1.com/web/ folder. If not then it will probably be in the wp folder. And you may want to move it, see below.

Now you have installed Wordpress in to your Bedrock Project, you can upload it to github for others to collaborate if necessary.

So from root folder run

$ git add . && git commit -m 'First commit'

Your folder structure inside the vhost1.com directory should now look as below.

config

│ ├── application.php

│ └── environments

│ ├── development.php

│ ├── production.php

│ └── staging.php

├── vendor

├── web

│ ├── app

│ │ ├── mu-plugins

│ │ ├── plugins

│ │ ├── themes

│ │ └── uploads

│ ├── wp

│ └── wp-config.php

Or the wp-config.php may be inside the wp folder, you might want to move it to the web folder if this is the case, see below for reason.

config: this is where you configure WordPress. These files can't be accessed from the Internet.

config/application.php: this file contains the usual WordPress configuration and is intended to include base settings that are common to all environments.

config/environments/*: these contain environment-specific settings. For example in production it disables errors output.

vendor: dependencies managed by Composer will be installed there, except WordPress plugins and themes; if you inspect the composer.json file you'll see that these kind of packages will be moved in web/app/{mu-plugins,plugins,themes}/.

web: files included in this directory are publicly available
— only the files that are required are in the web folder (see

config

above).

web/app: this is the old wp-content folder. It's been renamed to reflect its content. This is where your plugins and themes will end up.

web/wp: the WordPress package. This should be put in vendor but can't be because of WordPress limitations.

web/wp-config.php: this file is well-known, in Bedrock it acts as a loader to load settings from the config directory. It needs to stay here because WordPress core hard codes paths.

Environment Settings.

the “.env” file is ignored by git which is a benefit. It also allows you to define a different password/key for each machine. If every developer has to generate a new one for testing purposes and the key is stored in a file that's tracked by git you have to remember not to add that file to the staging area.

So add it to the .env file

DB_PASSWORD=<password>

And define it in the config file

define ('DB_PASSWORD', env('DB_PASSWORD'));

Environment-specific files (`config/environment/ are required before the main file ('config/application.php') So you cant override settings.

If you have the same configuration for development and staging but a different one for production, then do the following.

define it in every environment file (`development.php`, `staging.php`, `production.php`, etc).

put it in the `.env` file and define it in the main application (`application.php`) file.

Plugins

If your plugin is available in the official plugin registry, you can install using Composer and WordPress Packagist, which is a Composer repository that mirrors WordPress' official plugin and theme registry.

Bedrock has added wpackagist's repository, so installing a plugin is just a matter of running the following command to install the latest version

$ composer require wpackagist-plugin/<name>

$ git add composer.json composer.lock

$ git commit -m 'Install <name> plugin'

Plugins are prefixed with wpackagist-plugin/ so the plugin Memberful WP becomes wpackagist-plugin/memberful-wp.

You can also provide a constraint for the plugin version no.

$ composer require wpackagist-plugin/memberful-wp ~1.0

$ git add composer.json composer.lock

$ git commit -m 'Install Memberful plugin'

You can also do the same if you manually edit the composer.json file and run

composer
install

If your plugin isn’t available on the official registry, you will need to put it in `web/app/plugins` and remove it from the ignore list:

$ echo '!/web/app/plugins/my-plugin' >> .gitignore

$ git add .gitignore web/app/plugins/my-plugin

$ git commit -m 'Add Plugin'

If you have a git repository for the plugin, you can use Composer directly. Add the following to the repositories array of the composer.jsonfile

composer.json

{

"type": "git", "url": "<repository url>"

}

The repository needs to contain a `composer.json` manifest file in the root.

composer.json

{

"name": "Plugin name", "description": "Plugin description", "type": "wordpress-plugin", "license": "proprietary",

"require": { "php": ">=5.5", "composer/installers": "~1.0.12" }

}
You can run

composer
require plugin-name

to
install it.

And
activate it from wp-cli

$
wp-plugin activate plugin-name

If
plugins ask you to modify the

wp-config.php

file,
move those new settings to `application.php`, or the environment
specific one.

Themes

Themes work the same way as plugins, with two differences:

Their directory is web/app/themes

Composer's vendor name is wpackagist-theme

If you use a theme that's available on the official WordPress registry you can install it with Composer:

$ composer require wpackagist-theme/hueman

If you're going to develop your own theme, create its folder under web/app/themes and you're good to go.

There is much more that you can do with Bedrock including deploying with Capistrano

However here we are just looking at setting it up in a VirtualHost Server for initial local testing. If you followed the above successfully then you are up and running.

Set Up Wordpress CLI Tool On Centos 7 RHEL

noreply@blogger.com (Paul Anthony McGowan) — Sun, 19 Nov 2017 12:20:00 +0000

Wordpress CLI tool is very useful for performing many tasks associated with Wordpress development and administration. its easily installed and configured if your system meets the minimum requirements.

So make sure your system meets the minimum requirements before installing it.

UNIX-like environment (OS X, Linux, FreeBSD, Cygwin)

PHP 5.3.29 or later

WordPress 3.7 or later

Once you've established these, download the wp-cli.phar file using curl or wget.

$ curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar

Check it with the following command.

$ php wp-cli.phar --info

Make it executable and move it into your path so you can use the wp command.

$ chmod +x wp-cli.phar

$ sudo mv wp-cli.phar /usr/local/bin/wp

Run a command to check its installed properly

$ wp --info

PHP binary:    /usr/bin/php
PHP version:    7.0.25
php.ini used:    /etc/php.ini
WP-CLI root dir:    phar://wp-cli.phar
WP-CLI vendor dir:    phar://wp-cli.phar/vendor
WP_CLI phar path:    /home/anton
WP-CLI packages dir:
WP-CLI global config:
WP-CLI project config:
WP-CLI version:    1.4.1

Check out the quick start guide at https://make.wordpress.org/cli/handbook/quick-start/

to get started with it.

That's it!, you can now use the wp-cli tools for many tasks associated with Wordpress.

Set Up Virtual Hosts for Apache On Centos 7 RHEL With Extra File And Folder Permissions

noreply@blogger.com (Paul Anthony McGowan) — Sun, 19 Nov 2017 11:40:00 +0000

Many of us don't have computers powerful enough to run some of the Virtual Machine and Container solutions out there properly for developing applications, or prefer to use a traditional server on the host machine for this purpose.

Here we look at a solution for setting up extra VirtualHosts on a standard Linux (Centos 7 or RHEL) machine using Apache Web Server, which is expandable, ie, you can create extra Virtual Hosts as you require by repeating many of the same steps.

This is extremely useful in many scenarios and as you can create as many VirtualHosts as you want and you can set up a different one for every development environment you are using. Assuming you are not at high security on your machine, below is all you need to do, if not there may be extra steps to perform which are not covered here.

It is assumed that you have the standard Apache (Httpd) installed and running correctly at the usual localhost (probably port 80) with default folders at /var/www/html for RHEL or Centos.

There are plenty of tutorials for setting that up online, if you do not, then do this first!

PHP is not necessary for a VirtualHost but I've added a bit for users who want to check that is working also, if they have it.

We will be setting up a new Virtual Host and domain name with its own folders and permissions for easy access to them from your desktop without having to use sudo .

You can also use this tutorial to change the permissions and access location for your existing /var/www/html folders even if you are not setting up a Virtual Host by following steps 2-8 after first creating the new group www-data and adding the users apache and user, as in the preliminary task immediately below.

If you are setting up a new VirtualHost then use steps 1-14 after this.

Preliminary Task.

The first task is to set up a new group called www-data, so that both you and apache can access and change files without you having to use sudo all the time.

So create a new www-data group and add users and apache to it.

$ sudo groupadd www-data

Add the users to group

$ sudo usermod -a -G www-data anton (change anton for your user)
$ sudo usermod -a -G www-data apache

Check it with

$ groups apache anton (change anton for your user)

Should show both you and apache as users for the new group.

You only have to do the above once regardless of how many virtual hosts you are setting up and its probably a good idea to do it on just a standard apache install anyway.

Primary Tutorial

(2-8 for standard apache access, change vhost1.com to html, or 1-14 for full VirtualHost setup read verbatim)

Now set up the directory for the new vhost server and files

1. $ sudo mkdir -p /var/www/vhost1.com

The permissions, we fix these so that both apache and user have access to change files, so change the group of this directory to the new www-data group and allow apache access to read & write files.

2. $ sudo chgrp -R www-data /var/www/vhost1.com
3. $ sudo find /var/www/vhost1.com -type d -exec chmod g+rx {} +
4. $ sudo find /var/www/vhost1.com -type f -exec chmod g+r {} +

Now change ownership to your user so you can also read & write files easily.

5. $ sudo chown -R anton /var/www/vhost1.com   (change anton for your user)
6. $ sudo find /var/www/vhost1.com -type d -exec chmod u+rwx {} +
7. $ sudo find /var/www/vhost1.com -type f -exec chmod u+rw {} +

Now create symlink to your desktop for easy access to add and alter files, you don't now need to use sudo.

8. $ ln -s /var/www/vhost1.com /home/anton/Desktop (change anton for your user)

(Optional, repeat steps 2-8 on your existing standard apache folder at /var/www/html for parity, just change vhost1.com to /html, these will also add that folder to the desktop with the new group and user permissions) so you can have your standard folder set up plus the new VirtualHost folder as well, (and any you add later) all on your desktop)

To finish this part, add an index.html file into vhost1.com directory (now its on your desktop) with below contents.

<html>
<head>
    <title>Welcome to vhost1.com!</title>
</head>
<body>
    <h3>Hello, your virtual host is set up correctly.</h3>
</body>
</html>

Optional, you can also add a phpinfo page to check your php details, create a php file in vhost1.com directory called info.php with the usual php function in it.
<?php
phpinfo();
?>

You can check this when you've finished the set up, but first we set up the VirtualHost.

We will need to set up the directory that all the virtual hosts will be stored in, as well as the directory that tells Apache that a virtual host is ready to serve. The sites-available directory will keep all of our virtual host files, while the sites-enabled directory will hold symbolic links to virtual hosts that we want to publish.

Make both directories with:

$ sudo mkdir /etc/httpd/sites-available
$ sudo mkdir /etc/httpd/sites-enabled

You dont need to set any permissions on these, just leave as is & you only need to do it once regardless of how many VitualHosts you are setting up.

Now tell Apache to look for virtual hosts in the sites-enabled directory. To do this, we will edit Apache's main configuration file and add a line declaring an optional directory for additional configuration files:
$ sudo nano /etc/httpd/conf/httpd.conf

Add this line to the end of the file:

IncludeOptional sites-enabled/*.conf

(Only once for the above)

Now set up the first VirtualHost file, it has to end in .conf

9. $ sudo nano /etc/httpd/sites-available/vhost1.com.conf

Into this file add the VirtualHost directive as below

<VirtualHost *:80>
    ServerName www.vhost1.com
    ServerAlias vhost1.com
</VirtualHost>

Now add the document root which is the directory you created earlier, and optional logs

DocumentRoot /var/www/vhost1.com
ErrorLog /var/www/vhost1.com/error.log
CustomLog /var/www/vhost1.com/requests.log combined

So the final file looks like this.

10.
<VirtualHost *:80>
    ServerName www.vhost1.com
    ServerAlias vhost1.com
    DocumentRoot /var/www/vhost1.com
    ErrorLog /var/www/vhost1.com/error.log
    CustomLog /var/www/vhost1.com/requests.log combined
</VirtualHost>

Now enable the file and site for apache to find and use,
11. $ sudo ln -s /etc/httpd/sites-available/vhost1.com.conf /etc/httpd/sites-enabled/vhost1.com.conf

This creates a symlink to the file in sites-available inside the sites-enabled folder you created earlier.

Now find your Ip address for your machine with

$ ifconfig | grep -Eo 'inet (addr:)?([0-9]*\.){3}[0-9]*' | grep -Eo '([0-9]*\.){3}[0-9]*' | grep -v '127.0.0.1'

Add it to your /etc/hosts file along with the name of your new VirualHost server.
12. $ sudo nano /etc/hosts

Add the line as below
192.168.1.218 vhost1.com   (change for your ip and virtual host server name.

Restart apache
13. $ sudo service httpd restart

14. Browse to your new server/site using

http://vhost1.com

Optionally, check your php details by browsing to the info.php file if you created it.

You can repeat steps 1-14 for every extra VirtualHost you want to set up, just change the values ie, vhost1.com to vhost2.com and so on.

You don't have to create the index.html files or info.php files but it is recommended so you can check the site is working properly.

(Technically, this adds 2 extra steps to 1-14 above!)

So the above should work on most Centos 7 RHEL machines as is, and some other Linux distros depending on the apache installation path and folder locations which you may have to alter for those distros.

Hope it helps!

Make A Translucent Back To Top Button For Responsive Web Site or Mobile App

noreply@blogger.com (Paul Anthony McGowan) — Sun, 12 Nov 2017 19:43:00 +0000

Whilst there are plenty of options if you want to put a back to top button on your website, many of them use external SVG or other type image files for the marker image.

You can add a responsive translucent Back To Top button which becomes just visible as site visitor starts scrolling down the page easily with a few lines and just a button element with a Font Awesome icon.

While I used a Bootstrap container in this example, it works fine on standard html pages as well. Also useful for mobile apps if the framework you are using doesn't have one.

Start with the html page, just a standard page including the Font Awesome CDN link, and links to your app or main js and style css files.

1. HTML Page code starts like this.

<doctype html="">
<html lang="en">
<head>

<title>Back To Top Translucent Button</title>

<link crossorigin="anonymous" href="https://maxcdn.bootstrapcdn.com/bootstrap/4.0.0-alpha.6/css/bootstrap.min.css" integrity="sha384-rwoIResjU2yc3z8GV/NPeZWAv56rSmLldC3R/AZzGRnGxQQKnKkoFVhFQhNUwEyJ" rel="stylesheet"></link>

<link href="https://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css" rel="stylesheet"></link>

<link href="css/style.css" rel="stylesheet"></link>
</head>
<body>
<div class="container">
    <div class="jumbotron">
        <h3 class="text-center">
        Floating translucent back to top arrow for long or short pages using standard js & Font Awesome
</h3>
<div class="blockquote">
        Page content, put it in here or a lot of lorem ipsum to test it out.

</div>
</div>
</div>

<button id="topBtn" onclick="topFunction()" title="Go to top"><em class="fa fa-2x fa-chevron-up"></em></button>

<script src="js/main.js"></script>
</body>
</html>

Button has an onclick topFunction and a FA icon which can be changed and resized.

2. Add the css to style the button in your linked stylesheet file

#topBtn {
display: none;
position: fixed;
bottom: 20px;
right: 20px;
z-index: 99;
border: none;
outline: none;
background-color:transparent;
/*Optional color the button
color:rgba(128, 128, 128, .7);*/
}
#topBtn:hover {
background-color:#transparent;
}

The button is fixed to the bottom right of page with transparent background, this will show a solid button icon image which you can make translucent by optionally using the included rgbs settings with the last value say somewhere between .4 to .7.

3. Add javascript functions for the scrolling and clicking actions in your linked js file.

window.onscroll = function() {scrollFunction()};
    function scrollFunction(){
        /*Change timer to suit page size*/
        if (document.body.scrollTop > 1000 || document.documentElement.scrollTop > 1000) {
            document.querySelector("#topBtn").style.display = "block";
        } else {
            document.querySelector("#topBtn").style.display = "none";
        }

    }
    function topFunction() {
          document.body.scrollTop = 0;
          document.documentElement.scrollTop = 0;
    }

The timer can be adjusted according to page content size and set for the button to start appearing as the user gets further down the page.

Button appears unobtrusively at bottom right . It doesn't actually need bootstrap css or js, nor jQuery to work fine.

Clone the code example at https://github.com/minimallinux/backtotopbutton.git

A nice easy to implement back to top button.

Build A Software Defined Data Center With Red Cloudforms And Openstack Part 1 & 2 & Android Versus iOS Application Build Choice

noreply@blogger.com (Paul Anthony McGowan) — Fri, 03 Nov 2017 08:33:00 +0000

MariaDB Maxscale Configuration, The 10 Best Linux Distributions & Using Firebase For iOS Apps

noreply@blogger.com (Paul Anthony McGowan) — Thu, 02 Nov 2017 09:21:00 +0000

Win An Honor 6x, GunboundM On Android iOS, Essential Phone

noreply@blogger.com (Paul Anthony McGowan) — Fri, 27 Oct 2017 08:26:00 +0000

MS SQL On Linux, PostgreSQL On Centos & AWS Openshift RHEL

noreply@blogger.com (Paul Anthony McGowan) — Fri, 27 Oct 2017 08:00:00 +0000

Best Centos Repos, Apache On Centos & Microsoft Joins Linux

noreply@blogger.com (Paul Anthony McGowan) — Thu, 26 Oct 2017 08:14:00 +0000

One Plus Android, Nokia 5 Review & Best Android Nougat Phones

noreply@blogger.com (Paul Anthony McGowan) — Thu, 26 Oct 2017 07:53:00 +0000

Users still stuck with Android Marshmallow, Xiaomi release stock Android powered Smartphone & Google launches Chrome Enterprise.

noreply@blogger.com (Paul Anthony McGowan) — Wed, 23 Aug 2017 07:46:00 +0000

iOS Developer 11 Beta Released, 7 Of The Best Free iPhone Apps & Learn To Code in 3 Months.

noreply@blogger.com (Paul Anthony McGowan) — Tue, 08 Aug 2017 06:52:00 +0000

Windows 10 Links Android Phone To A PC, Gboard For Android TV Report & Stock Android No Longer best Version Of Android.

noreply@blogger.com (Paul Anthony McGowan) — Sun, 06 Aug 2017 08:06:00 +0000

3 Best Linux Systems For Old Computers, Tails 0.22 Secure Operating System & Running Your Business On Linux.

noreply@blogger.com (Paul Anthony McGowan) — Wed, 02 Aug 2017 06:58:00 +0000

Windows Or Linux, Which Is Better ?, The Year Of Linux Desktop & Linux Mint 18.3 Review.

noreply@blogger.com (Paul Anthony McGowan) — Tue, 01 Aug 2017 07:21:00 +0000

Apple Store Outperforms Google Play Store, Android 0 Roundtable Brings Changes & vmWare Create Linux OS.

noreply@blogger.com (Paul Anthony McGowan) — Mon, 31 Jul 2017 06:47:00 +0000

Happy Hacking Linux Dual Boot With MacOS, Ubuntu Mate 17 Released & SparkyLinux 5 All - Purpose Distro Review.

noreply@blogger.com (Paul Anthony McGowan) — Sat, 29 Jul 2017 07:25:00 +0000

Chromebook Workstation Runs Android Apps, Facebooks Reaches 2 Billion Users & 10 Things In Tech To Know.

noreply@blogger.com (Paul Anthony McGowan) — Fri, 28 Jul 2017 09:05:00 +0000

Setup vmWare vCentre On Mac Or Linux, Dell 5720 Linux Workstation & Microsoft Bring SQL Server To Linux.

noreply@blogger.com (Paul Anthony McGowan) — Wed, 19 Jul 2017 02:43:00 +0000

Moto Z2 Play Review, Android 8 Coming Soon & Nokias Android Phones Finally Arrive.

noreply@blogger.com (Paul Anthony McGowan) — Mon, 17 Jul 2017 08:38:00 +0000

Samsung Galaxy A5 Gets Android Nougat, Android Nougats Panic Button & Train To Be an Android Developer In 2 Days !

noreply@blogger.com (Paul Anthony McGowan) — Mon, 17 Jul 2017 08:31:00 +0000

Microsofts AI Powered App For Blind On iOS, Dictate Text Messages To Your Phone & 32 Best android Apps To Download.

noreply@blogger.com (Paul Anthony McGowan) — Mon, 17 Jul 2017 08:19:00 +0000

Google Pixel 2 Update, Facebook Find Hidden Messages You Havent Seen Before & Upcoming Smartphone Tech.

noreply@blogger.com (Paul Anthony McGowan) — Mon, 17 Jul 2017 08:11:00 +0000

A Review Of iOS 14, Free PDF Editor For All OS Systems & Google Desktop Tool For Backup Available On PC And MacOS.

noreply@blogger.com (Paul Anthony McGowan) — Mon, 17 Jul 2017 08:01:00 +0000

GIFroll Brings Animated Gifs TO iOS 10, How To Access A Locked iOS Device & Safari Is The Fastest Browser For iOS Systems.

noreply@blogger.com (Paul Anthony McGowan) — Sat, 15 Jul 2017 08:14:00 +0000