Forum


Replies: 1   Views: 261
Licensing for development and production
Topic closed:
Please note this is an old forum thread. Information in this post may be out-to-date and/or erroneous.
Every phpdocx version includes new features and improvements. Previously unsupported features may have been added to newer releases, or past issues may have been corrected.
We encourage you to download the current phpdocx version and check the Documentation available.

Posted by nylontechnology  · 15-02-2019 - 21:40

I'm hoping this is not a repeat, but I have read every post in this topic and still need clarification. 

We purchased a Premium license.

When this goes live, the URL will be www.clientname.com, but it might be different.

However, we need to set this up for local development and QA.

Important! Our applications are URL based, not IP based. So, for example, we need to use https://clientname.local on our development workstations.

Other answers in this topic all say the same thing, which I think needs to be clarified. Also, we can use this new thread to create a definitive guide so people don't always ask the same question!

  • The purchased subdomain (Basic licenses), domain and its subdomains (Advanced and Premium licenses) or IP (Premium licenses)
  • localhost
  • private networks (classes A, B and C)

The above leaves a lot of questions remaining, so here is what I think they might  mean. Please confirm.

  • The purchased subdomain (Basic licenses), domain and its subdomains (Advanced and Premium licenses) or IP (Premium licenses)
    • ​This makes sense for production, but it seems we can't assign the license yet since we need to use URLs for local development?
  • localhost
    • ​Does this mean on our local dev workstations we need to use http://localhost to access the development?
  • private networks (classes A, B and C)
    • ​Does this mean that we can use, for example, http://10.10.0.21 as the sitename?

During the license purchase process we made the domain name "localhost" since we weren't sure how the licensing worked.

Can we leave this as localhost and use https://clientname.local on our workstations?

Or, can we assign the license to what we think the client domain will be and then use local hosts file so we can use the correct domain in our dev workstation environment?

Thanks!

J

 

Posted by admin  · 16-02-2019 - 09:11

Hello,

Let's try to clarify your questions:

The purchased subdomain (Basic licenses), domain and its subdomains (Advanced and Premium licenses) or IP (Premium licenses)

  • This makes sense for production, but it seems we can't assign the license yet since we need to use URLs for local development?

All licenses can run on private networks (classes A, B and C) for development, it doesn't matter if the URL is an IP (such as 192.168.*, 172.16.*, 10.*) or a local domain, as a local domain resolves to a private network IP range it will work perfectly too.

localhost

  • Does this mean on dev workstations we need to use http://localhost to access the development?

This means you can use localhost (as domain name or 127.0.* IP) for development. And you can also use private networks (classes A, B and C) for development.

private networks (classes A, B and C)

  • Does this mean that we can use, for example, http://10.10.0.21 as the ​sitename?

Yes, that IP can be used for development with the same license.

Can we leave this as localhost and use https://clientname.local on our workstations?

Or, can we assign the license to what we think the client domain will be and then use local hosts file so we can use the correct domain in our dev workstation environment?

Both questions are right. You can set localhost as domain name and do the development on localhost and private networks, and then change the domain name to the definitive one. Or choose the definitive domain when purchasing the license and to the development in localhost and private networks for development.

In short, a license can be used in:

  • The purchased subdomain (Basic licenses), domain and its subdomains (Advanced and Premium licenses) or IP (Premium licenses)
  • localhost: as IP or localhost name
  • private networks (classes A, B and C): as IP or local domain name
  • Any number of servers in localhost and private works fordevelopment
  • A single server for production use

Regards.