Situation:
When the Community Edition is downloaded, it's initially accessible only using using Localhost as the Hostname domain. This works fine if the Test Website is on the local machine, but can create problematic issues if testing is on a remote machine. Although it's possible to re-direct "localhost" using Hosts or local DNS, in my case I'm also crossing a Proxy Firewall which itself is re-directing web requests to different machines and webservers based on the hostname. Creating and flipping configurations just for testing and back to their original settings on 3 places (client, firewall and website) multiple times is very inconveinent.
Request:
1. Would like to suggest that all Community Edition downloads automatically include a license that supports at least another Hostname than "localhost." I'm recommending something like "localhost-10" but can be almost anything that's not likely already used. This at least allows the special hostname to be configured and can be left alone afterwards instead of repeatedly creating and undoing configurations.
2. Alternative solution might be to embed by default a restriction for 25 products which can be modified only with an issued license. If there is little or no reason to track free storefronts, this should eliminate "housekeeping" for such deployments.