Best practice for "testing" vbDrupal?

[Jeff Hester]

Does anyone have recommendations for testing vbDrupal without adversely impacting a production environment?

Should I just create a copy of the database and the entire website for testing?

[tamarian]

Yes, a test environment is best, as in a home server.

But it can also be done on a production environment, as vB Drupal does not update vBulletin tables. The only exception is announcing new content in a new thread, which you can disabled, or setup to announce in a private forum.

[hammerFar]

btw: if you're looking for an easy way to test LAMP applications, the XAMPP is a nice approach:

http://www.apachefriends.org/en/index.html

(haven't tested with vB Drupal though, but would expect it to be compliant)

[emiratesmac]

I installed Drupal, vBulletin, and finally vbDrupal without much trouble on my PowerBook running 10.4.6. I already had LAMP up and running (Apache with PHP comes on every Mac standard). I was already using it as a test-bed for Drupal. Makes it easier when you can try templates and stuff there before "going live"... ;-)