License conditions page:
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.
- 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 use localhost or private networks fordevelopment.
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 networks for development
- A single server for production use