+1 for installing vBulletin locally.
Regarding databases, tThe typical rule of thumb is each application gets its own database. vBulletin is a little older, so it has support for sharing a database with other applications. This can be accomplished by prefixing the application's tables.
For example, if both wordpress and vBulletin installed, they could share a database.
wp_* tables belong to wordpress
vb_* tables would belong to vBulletin
This way there is no chance of both applications having a 'user' table or another common one.
Even if you only plan on having vBulletin, you may start installing other related applications on the same site which may not use vBulletin. For example: links system, gallery system, e-commerce, etc. Using 25 for a single site is extremely unlikely however.
Cheers
|