Best Way From Test to Production?
 

We are modding a vbulletin site first on our test domain and then when the mods are proven we make the mod to our live domain. Aside from the database changes, can we just copy the vBulletin directory /forums/ from our test site over to our live /forums/ or do we need to manually set each mod back up on the live site as well?

What strategies are people using and what is the best practice for mod promotion from test to production?

Im kind of curious about this myself... I guess vb 3.5's hook system will eliminate alot of this but yeah, still good to know.

Generally, when I start a mod, I pull the relevant files from my live server to my development/test computer. I make and test the changes and then reupload the files and make the database changes on the live server.

Thats what I am doing atm but I rename the original file on the server so its there should I or another need to fix it in case something pops up.

Based upon the experience I just had with modding in the vbAdvanced CMS Portal I would have to say that it depends on the complexity of the mod.

The vbAdvanced CMS is easy enough to install (I think it took about an hour to go from no domain, to domain, to vBulletin, to vbAdvanced.) This one can be copy pasted without too much trouble. There's a few files you'll have to rename/restore before you do it and those will be obvious.

I don't see any reason for the direct copy to not work in most cases. I suppose a dry-test on a dumb-domain ahead of time would be a safe bet just to make sure you had the method correct.

There is no problem moving files from one server to another but you must be careful (110% sure) that the files are equivalent. In most cases, I recommend against this -- it is better to be safe than sorry.

When I start a mod, I do it on my local computer.

Every line that I modify (vb file) I wrap with the following:
//==========================\\
// == [ HACK A - GTP ]
enter code here
// == [ 00-00-2005 ]
//==========================\\

This allows me to search for 'modified' sections at a later time with a script that I wrote. The script searches for specific phrases (ie. 'hack a', 'GTP', etc) in a file and displays any file(s) that have been modified. From there, I just have to look at the files for the above comments (wrap). This works online/offline.

This allows me to quickly document my modifications. (I document every modification that I do.)

Thanks everyone for your comments/help. Sorry for taking a while to get back here.

This is a great idea. If the mod requires a change rather than an addition, do you leave the original phrase included in comments? One problem I found is when several complex mods are installed subsequent and they change the same portion of the script.

Perhaps the solution is commenting out the original phrases tagging them as original and then commenting out each subsequent mod change, thus leaving a trail for that particular phrase would help to keep track. That would add a lot of code though. I suppose I could keep an archive copy of all the changes and just single reference to the previous hacks in the production file.

It all depends ... if it's a large modification I replace the whole thing.
I already know it's been modified so it doesn't matter if I remove the original code.

However, if it's a small modification (1-3 lines) I comment out the original code.
It helps when upgrading the forum.

You should do what is easier for you.

I have added my script into the CODE MODIFICATIONS forum.
https://vborg.vbsupport.ru/showthread.php?t=81524