Planning Your Site Stack
1. Create a directory.
(usually under the www or public_html dirctory)
We start with the number 1 since we know that once you get started with WPSiteStack and find out how easy it is to setup a new site you’ll start making several of these directories (stacks). In theory you can keep piling sites on this one directory, but soon you’ll find it more useful to group sites together by type. At that point you might start naming directories by type i.e wpsitestack-blog, wpsitestack-cms, wpsitestack-portfolio, etc.
2. Install WordPress in this directory
Don’t use your hosts “1 click installer”. This is to avoid any version update notices from the third party one click installer. WordPress now has it’s own updater which most “1 click installer” scripts don’t know about, so these installers are trying to do you a favor by informing you that there is an update available even though your site is already up to date, which ends up just being a pain.
It’s best not to use the default WordPress installation for any of your actual domains. That way all of your actual (or important) domain will be managed by WPSiteStack.
The best way to start is to use your control panel to create a subdomain of your primary domain name. (The primary domain is the domain you use to log into your control panel). Name the subdomainsomething like this:
This will usually create a directory named ‘wpsitestack1’ in your web directory (www or public_html). This where you’ll install the base installation of WordPress. Noone, but you will ever see this domain really, but it’s good to set it up and call it something like ‘My Default Site’. That way if something goes wrong with domain name mapping you see it and realize immediately that something is wrong. In this case it’s usually a quick typo fix or something to get everything working.
Here’s a little video if you don’t know how to install WordPress yourself. Remeber you want to the directory name to match that subdomain you used.
To do the configuration on the default (or base installation). You can access the base install by using the sub domain that the control panel configured for you. For example:
In the wp admin area of the base install, name the site Default and use the default theme. This is very useful to make sure an added domain is mapped correctly. If you make a typo or something in WPSiteStack is not right, then this default site will show up, making it obvious that there is something wrong with the WPSiteStack entry allowing you to correct the problem quickly.
You do need to go though the regular configuration process and setup the database, but just name the site “Default”. Set permalink to anything you want accept default, you do not want to use default. Remember all sites must use permalinks or none of them can.
3. Install WPSiteStack
4. Map domains or subdomains to the wpsitestack1 directory after you setup the domain with WPSiteStack.
Here is what a typical directory structure looks like:
All addon domains will need to be setup to use this same wpsitestack1 directory. Control panels typically create a new directory for each domain, but you can over ride this to point to our WPSiteStack directory. If you are hosting domains the you do not require WordPress you just install them in the usual way (ex: domainone directory).