Some of the guys at The Roost found this old valve amplified record player on the side of the road during council cleanup. 
The needle in the record player was broken, but otherwise it worked fine. Now it’s had some modifications such as the installation of a motherboard, old touch pad keyboard, usb port and a 2nd hand LCD screen attached to it’s lid. So now it plays digital audio and video. Sounds nice too.
This an amalgamation of the information found on the following pages:
I don’t have the confidence to submit this to the official docs, perhaps you do?
If you want to run a network of blogs you should at least have a basic understanding of UNIX/Linux administration. A basic knowledge of WordPress development, PHP, HTML and CSS is recommended as well.
Setting up and running a multi-site installation is more complex than a single-site install. Reading this page should help you to decide if you really need a multi-site install, and what might be involved with creating one. If the instructions on this page make no sense to you, be sure to test things on a development site first, rather than your live site.
Since this feature requires extra server setup and more technical ability, please check with your webhost and ask if they support the use of this feature. It is not recommended to try this on shared hosting.
You are given the choice between sub-domains or sub-directories in Step 4: Installing a Network. This means each additional site in your network will be created as a new virtual subdomain or subdirectory.
site1.example.com and site2.example.comexample.com/site1 and example.com/site2
At the time of writing I have not tested sub-directories with nginx.
It is also possible later, through use of a plugin such as WordPress MU Domain Mapping, to map individual sites to independent domain names.
localhost.(See wp-admin/network.php for more detail)
Your WordPress will be updated when creating a Network. Please backup your database and files.
(If this is a Sub-directories Install, skip this step.)
Sub-domain sites work with the use of wildcard subdomains. This is a two-step process:
nginx.conf file.server_name example.com 123.456.789.10;
A *.example.com
External links:
To enable the Network menu item, you must first define multisite in the wp-config.php file.
Open up wp-config.php and add this line above where it says /* That's all, stop editing! Happy blogging. */:
define('WP_ALLOW_MULTISITE', true);
This will enable the Network menu item to appear in the Tools menu. Visit Administration > Tools > Network to see the screen where you will configure certain aspects of our network.
Tools Network SubPanel
site1.example.com and site2.example.comexample.com/site1 and example.com/site2example.com. Double-check they are correct and click the Install button.
You may receive a warning about wildcard subdomains. Check Setting Wildcard Subdomains.
Warning! Wildcard DNS may not be configured correctly!
The installer attempted to contact a random hostname (13cc09.example.com) on your domain.
To use a subdomain configuration, you must have a wildcard entry in your DNS. This usually means adding a * hostname record pointing at your web server in your DNS configuration tool.
You can still use your site but any subdomain you create may not be accessible. If you know your DNS is correct, ignore this message.
The rest of the steps are ones you must complete in order to finish. You are going to ignore the last message about adding to the .htaccess file!
Tools Network Created
wp-config.php. blogs.dir directory under /wp-content/ wp-content directory. wp-config.php file. wp-config.php file while you are logged in to your sites admin panel. /* That's all, stop editing! Happy blogging. */. define('WP_ALLOW_MULTISITE', true); line only if you wish to remove the Network menu in the admin area. You may choose to leave this to be able to access the .htaccess rules again.. ... #access_log logs/host.access.log main; location ~* ^.+\.(xml|jpg|jpeg|gif|png|ico|css|zip|tgz|gz|rar|bz2|doc|xls|exe|pdf|ppt|txt|tar|mid|midi|wav|bmp|rtf|js|swf)$ { root /usr/share/nginx/html; rewrite ^/files(/.*)$ /wp-content/blogs.php?file=$1 last; expires 10d; break; } location / { root /usr/share/nginx/html; index index.html index.htm index.php; if (!-e $request_filename) { rewrite ^.+/?(/wp-.*) $1 last; rewrite ^.+/?(/.*\.php)$ $1 last; rewrite ^(.+)$ /index.php?q=$1 last; } } ... location ~ \.php$ { rewrite ^/.*(/wp-.*/.*.php)$ $1; root html; fastcgi_pass 127.0.0.1:9000; fastcgi_index index.php; fastcgi_param SCRIPT_FILENAME /usr/share/nginx/html$fastcgi_script_name; include fastcgi_params; } ... 4. Restart Nginx
You will now see a new menu section called Super Admin. The menus contained in there are for adding and managing additional sites in your network. Your base WordPress install is now the main site in your network.
Go Super Admin > Options panel to configure network options, and then create sites and users.
Here are some additional things you might need to know about advanced administration of the blog network.
Unlike Single Site WordPress, which can work with “ugly” Permalinks and thus does not need Mod Rewrite, MultiSite requires its use to format URLs for your subsites. This necessitates the use of an .htaccess file, the format of which will be slightly different if you’re using SubFolders or SubDomains. The examples below are the standard .htaccess entries for WordPress SubFolders and SubDomains, when WordPress is installed in the root folder of your website. If you have WordPress in it’s own folder, you will need to change the value for RewriteBase appropriately.
SubFolder Example
# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
# uploaded files
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]
# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]
# END WordPress
SubDomain Example
# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
# uploaded files
RewriteRule ^files/(.+) wp-includes/ms-files.php?file=$1 [L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule . index.php [L]
# END WordPress