Second private test site

[Moof]

Hi,

I've got an existing vb site, and have a private development site which mirrors the main site plus has a bunch of additions, most of which are going to go onto the main site in due course.

The development site is remotely hosted, and doesn't have a debugger on it, but I've found a problem which haven't been able to solve without a debugger.

Must I buy a second vb licence so that I can load vb onto my local PC (which has a raft of debugging tools)?

I'm the only person using the development site, and would be the only person using my local version, which would be of a strictly temporary nature. It's behind a firewall, so there's no incoming traffic, but outgoing is allowed, so you'd get a notification.

Or, should I switch off the first development site, and change my notification of the dev site to match the ip of my local version for the 3 hours that this is likely to take?

Perhaps shoving my local installation in testvb directory be enough of a notification?

Would rendering the first test installation inoperable by renaming index.php and similar files be enough to ensure that I only had one test site? It would be immensely painful to delete everything.

Thanks.

[Jobe1986]

According to the license agreement, you are allowed to run a test site for each license so long as it is in a directory named "testvb" and is password protected so as to prevent others from being able to access it.