Multiple machine licensing (dev, qa, staging, production)

Poster: mc2
Dated: Tuesday April 13 2004 - 23:32:27 BST

The website I want to buy Milonic for is running on 4 machines with different domain information:

Development: dev.customerdomain.com (fake host file entry on my Windows2000 server machine)
Staging: customer.mydomain.com (on our development servers)
QA: [an IP address at the customer, changes frequently]
Production: http://www.customerdomain.com

Do I need to buy 4 licenses? The FAQ seemed to say: legally no; but it seemed like you needed to somehow know what domain and subdomain we are.

In the example above, we're using 2 different domain names, IP addresses, and a subdomain. This is the usual situation for the sites we develop.

Am I going to have any problems ...?

Thanks,
--Mark

Poster: John
Dated: Wednesday April 14 2004 - 0:01:48 BST

To be completely sure, I've asked Andy to answer this one.

Poster: Andy
Dated: Wednesday April 14 2004 - 9:09:28 BST

Hi,

Sub domains are a very grey area and one that can cause much confusion.

Basically it goes a little something like this:

If the sub domains are all located on the same web server using the same IP Address and the sub domains are all part of the same company there will not be a need for multiple licensing.

However, if the sub domain is configured for another server or if it promotes another company or individual then there may be licensing issues that need to be addressed.

Hope this helps
Andy

Poster: mc2
Dated: Wednesday April 14 2004 - 19:33:35 BST

Thanks, yes much confusion.

We need to have the same code running on 4 different machines -- all for the same PRODUCTION website. The other three machines are basically machines in the DEVELOPMENT process, not publically accessible: again, Dev, Staging, and QA.

I'm happy to buy a license of each PRODUCTION website, but it seems that there are "licensing issues that need to be addressed" that involve your protection schemes that may make the development "environment" tricky.

I'm a contact developer, the client will buy the license, but I still need to develop for FOUR machines, only ONE of which will be public. I'd like to know if this can be done with the client buying ONE license. Please clarify this specifically, thanks!

Poster: Halobox
Dated: Thursday April 15 2004 - 6:29:26 BST

Why would this be an issue?

As I understand the license, you would be entitled to run on the staging machines with the same license since they wouldn't be for profit or anything.

Since the DNS name would be different, you'll see the milonic menu item unless you supply a link on each page using a menu. It seems this would be an acceptable check in the promotion/change mgmt. process.

Poster: mc2
Dated: Thursday April 15 2004 - 18:54:38 BST

>Why would this be an issue?
I'm trying to find out and understand the issues, thanks.

If "you'll see the milonic menu item unless you supply a link on each page using a menu" is the ONLY issue, I can live with that.
Is that the only issue? And the right fix?

I didn't know that before, and have spent a good deal of time trying to find out. Thanks again.

Dev, staging and production license use

Poster: Halobox
Dated: Thursday April 15 2004 - 22:29:39 BST

My interpretation of the "DHTML Menu Licensing" section on the main homepage at http://www.milonic.com is that we are free to run the menu code on our dev and staging servers.

If we do, the MILONIC menu item will show for unregistered menu code unless you put a link somewhere on the html page to http://www.milonic.com. That's kewl with me because I know as the code gets propagated to the production server with the registered menu, the MILONIC menu item will magically disappear.

On my personal server, I'll be happy to advertise their product in trade for running the code. Nice logos at http://www.milonic.com/logos.php

Poster: Andy
Dated: Thursday April 15 2004 - 22:35:51 BST

For the record. Testing and evaluation can be done without a license. It's like a try before you buy kind of thing.

Once the site goes live and is in production though, licensing will become an issue.

Also, the free license is only available for non-profits and is under a self assessment scenario. Any abuse of this though is considered offensive and we deal with it in a number of ways.

Cheers
Andy.