License for development or test website.

We understand that a lot of our clients want to maintain a development or test site in parallel to a live one.

The licenses for our products are valid for one installation on one domain/subdomain.

If you want to have an extra development or test website, you have one of the two options:

1. You can install it on "test" subdomain of your live site's domain. e.g.

Live site is: http://www.example.com/

Dev site should be: http://test.example.com/

If your live site is on a subdomain e.g.

Live site is: http://courses.example.com/

Dev site should be: http://test.courses.example.com/

Note that is has to be "test", and not "dev" or "staging" or anything else. 

2. You can always purchase an extra license if your test domain doesn't meet the above criterion.

 

Note: example.com is just used for an example, you should replace example.com with your own domain. 

 

Setting up a test site on your localhost: 

If your test site is not on a public server, but is on your localhost, currently license cannot be setup when using localhost domain on your localhost. However, you can mimic your localhost to act as your test domain. You can do it by modifying the hosts file of your own computer and adding the following line to it:

127.0.0.1 test.example.com

Now if you access http://test.example.com from your browser, you will be seeing the site on your localhost, not the site on your live server. The change is only for your computer, and it doesn't effect the access to the domain from any other computer. 

 

Modifying the Hosts File:

Windows 8, Windows 7 and Windows Vista

Windows 8, Windows 7 and Windows Vista use User Account Control (UAC), so Notepad must be run as Administrator.

For Windows 8

  1. Press the Windows key.
  2. Type Notepad in the search field.
  3. In the search right click Notepad and select Run as administrator.
  4. In Notepad, open the following file:
    c:\Windows\System32\Drivers\etc\hosts
  5. Make the necessary changes to the hosts file.
  6. Click File -> Save to save your changes.

For Windows 7 and Windows Vista

  1. For Click Start -> All Programs -> Accessories.
  2. Right click Notepad and select Run as administrator.
  3. Click Continue on the "Windows needs your permission" UAC window.
  4. When Notepad opens Click File -> Open.
  5. In the filename field type:
    C:\Windows\System32\Drivers\etc\hosts
  6. Click Open.
  7. Make the necessary changes to the hosts file.
  8. Click File -> Save to save your changes.

 For Windows NT/2000/XP

  1. Click Start -> All Programs -> Accessories -> Notepad.
  2. Click File -> Open.
  3. In the filename field type:
    C:\Windows\System32\Drivers\etc\hosts
  4. Click Open.
  5. Make the necessary changes to the hosts file.
  6. Click File -> Save to save your changes.

Linux

1. Open a terminal window.

2. Open the hosts file in a text editor (you can substitute any text editor):

sudo nano /etc/hosts

3. Enter your password.

4. Make the necessary changes to the hosts file.

5. Press control-X (hold control and hit X), then answer y when asked if you want to save your changes.

 

Mac OS X 10.6 - 10.1.8

1. Open Applications > Utilities > Terminal.

2. Open the hosts file by typing the following in the Terminal window:

sudo nano /private/etc/hosts

Type your user password when prompted.

3. Edit the hosts file. The hosts file contains some comments (lines starting with the # symbol), as well as some default hostname mappings (e.g. 127.0.0.1 – local host). Append your new mappings underneath the default mappings.

4. Save the hosts file by pressing Control+x and answering y.

5. Make your changes take effect by flushing the DNS cache with the following command:

dscacheutil -flushcache

6. New mappings should now take effect.

 

 

 

 

 

Home | GrassBlade xAPI Companion | GrassBlade LRS

 

 

Have more questions? Submit a request

2 Comments

  • 0
    Avatar
    Kevin Walsh

    Does the subdomain have to be "test"? So if our site is example.com, we can only use the license on that and test.example.com? We cannot use it on dev.example.com or staging.example.com?

  • 0
    Avatar
    Pankaj Agrawal

    Kevin, You are right. It has to be "test"

Please sign in to leave a comment.
Powered by Zendesk