Administrative and Maintenance Tools - [ForumOps] vBulletin Development Environment

vBulletin Development Environment

vBulletin Development Environment (VDE) is a tool that allows you to build vBulletin products entirely from the filesystem. By using the filesystem, it allows you to follow best practises such as using version control, and simply working on actual files. Having to switch between browser windows and copy/paste is extremely inefficient.

This product has been updated to work with with vBulletin 3.5 and up to the latest 4.x series.

Runtime Environment

Assuming all of your files are in place, VDE checks your ./projects directory on every page load, and injects all of your projects' templates, plugins, etc. into memory and runs them as if they were natively installed into vBulletin.

Product Builder

VDE also comes with a project builder, which allows you to export your project into a standard product XML, and also any associated files with your project.

Open Source

This product is open source, and I encourage everyone who uses it to contribute back via GitHub.

Installation Instructions

Short version: upload files, import product XML. There are slightly different instructions based on whether or not you are running vBulletin 3 or 4.

Full instructions can be found at:
https://github.com/ForumOps/vBulleti...nt-Environment

I will not be posting any change logs or detailed instructions here, because they may change heavily with each version. Please refer to the GitHub page.

Disclaimer: this product was originally developed by SirAdrian / Adrian Schneider, who is part of our staff, and the primary maintainer of the product still.

[TheLastSuperman]

Awesome Adrian, thanks for releasing! - Installed!

If I weren't on staff I would nominate and vote for motm .

[ForumOps]

My pleasure.

Please note, I will be posting some simple modifications built with this over the next week or two to try and provide more useful examples as there is a bit of a learning curve the first time around.

[Adrian Schneider]

Would anyone be interested in having the ability to generate the filesystem stuff based on the product data in vBulletin? (reverse the build process)

Usage would be something like,

php vde.php import product_id

I need it myself, so will probably start that soon, but speak up if it's also useful for you so I can bump it up in the priority list.

[Blaine0002]

yes! copying phrases from the admin into seperate text files is a big PAIN!

[Andreas]

Awesome stuff

I thought about building smth. similar for a long time but never had enough time / interest to actually start developing.

You could avoid the file edit by changing

PHP Code:

vBulletinHook::$pluginlist[$hook] = 'global $vdeRuntime;' .
"\n" . '$vdeRuntime->listenAtHook("' . $hook . '");' .
"\n" . $hookObj->pluginlist[$hook]; 


to

PHP Code:

$this->_registry->pluginlist[$hook] = 'global $vdeRuntime;' .
"\n" . '$vdeRuntime->listenAtHook("' . $hook . '");' .
"\n" . $this->_registry->pluginlist[$hook];
vBulletinHook::setPluginlist($this->_registry->pluginlist); 


Nice, I'll try this out on my next vB project. :up:

[Sayid]

interesting mod, will try it soon in the summer holiday

[Adrian Schneider]

Thanks, Andreas. :up: I'll try to get that updated soon, as I hate file edits.

[Brandon Sheley]

Originally Posted by TheLastSuperman

If I weren't on staff I would nominate and vote for motm .

I voted for ya :up: