Understanding Sites & Scopes
NOTE: In previous versions of StrikeTracker, "Host" was the name used to refer to the delivery containers used to configure, cache, and deliver your content. With StrikeTracker 3.5, "Hosts" are now known as "Sites."
Every Highwinds StrikeTracker account (including sub-accounts) is provided with the ability to configure any number of what we call "Sites". Each Site has it's own delivery hash and base URL, which provides each of them with the ability to function as a stand-alone delivery product, with their own configurations, raw access logs, analytics, and hostnames.
Most commonly this is used to create multiple delivery environments, separating, for example, video libraries from image thumbnail libraries, or even different websites or games that are published by the same account owner.
Customers can also feel free to create new Sites for things like development and staging environments, getting full CDN delivery support during the testing and integration processes.
Each Highwinds Site can also have any number of Scopes defined. Scopes are pseudo-directories that correspond with directory paths of your objects, and are created so that configurations can be made to a sub-set of your files.
Say, for example, that your CSS files require different caching behavior than your images. You may want them to expire from cache every 1 hour, while the images should stay in cache for as long as possible. If these files are located in different directories on your server (or in Highwinds Cloud Storage), then you can add Scopes for these directories and then create different CDN Caching Policies for each location.
In this example you CSS file might be located at http://www.mydomain.com/styles/file.css, and your images are all in http://www.mydomain.com/images/ ... So you could create new Scopes called:
Once created, those Scopes will appear in Scopes dropdown at the top of the Site Edit Policies screen. Choosing one of those Scopes from the dropdown will move you to that Scope, and then allow you to add any configurations to just that scope. In this example you would then add a new CDN Caching Policy configuration with a 1 hour TTL for /styles/, and then switch to the /images/ Scope and add a new CDN Caching Policy with a 1 year TTL.
You may add any number of configurations to a Scope, but you do not have to add them all. Scopes will inherit configuration policies from their parents (and directories above them), so you only need to add new policies for those configurations that you want to explicitly overwrite for that Scope.
Note that Scopes must be a directory, they cannot be files themselves. If you need to apply policies to an individual file you will need to use the Path and extension filters available within that specific policy. Every Site also has a default Scope, labeled “/”.
Adding configuration policies to the “/” Scope will configure all objects for that Site. Generally you will add your policies to “/” first, creating default CDN behavior for the entire Site, and then create Scopes to and new policies in that Scope to override specific behavior such as cache rules or content protection.