Testing on a local server before deployment.

[SteveS]

How do most developers test the Easy PHP calendar before deployment to a public server? Before I deploy to a public server (www.companyname.com (http://www.companyname.com)) I fist develop in a local directory on my PC (virtual host dev.companyname.com) and then perform testing in another local directory on my PC (virtual host liv.companyname.com). Virtual host liv.companyname.com is an exact copy of what is transferred to the public server www.companyname.com (http://www.companyname.com) (hosted on a public server of my customer's choice).

With an expired license (on the local PC), I can verify the placement of the calendars and some other functionality, but I can't do much with filters and displaying items using the list mode (since only one item will display). Is there a special version available for development that has some feature disabled so it would be very undesirable to use on a public site but would enable developers to better test functionality? Right now, I have to troubleshoot on a public server (where the calendar is licensed). As with most developers, I prefer to develop on my local PC.

Any suggestions will be appreciated.

Thanks,
Steve

[Brian]

There isn't a limited license for local use. If this is something you do often, you may want to get a second license for the local PC. You would only need the regular license without options for testing.

[SteveS]

Thanks for the quick response - Purchasing one spare license for my local PC is not a problem, bit it seems that I would need a separate local license for each virtual host (dev.customer1.com, dev.costomer2.com, liv.customer1.com, etc) since the license is tied to a host name (unless I don't fully understand the licensing).

I realize I could probably change the paths within my PHP code to point to a central calendar for testing, but I prefer not to change anything after testing before going live (too much of a chance of a typo).

The method I am using is working, I just wanted to make sure there wasn't an easier way.

[Brian]

If the virtual host uses a different XXXXX.com domain, each would need it's own license. If you use the same domain, you'd only need one license.