This marks a MAJOR milestone.
The BMLT 2.0 server has a vastly improved (but very different) administrative interface. It has been redesigned from the ground up, to improve the basic workflow of Service Body Administrators.
Here is a basic user manual for the new interface. More will be revealed…
GETTING THE NEW CODE
The above link is a complete download. It contains all the code.
If you are adventurous, you can try the pre-release code:
NOTE: This is a source code page. You are best advised to use Git to download the trunk code.
The BMLT is kept under strict version control. This is a basic engineering best practice, and you can go back through every release of the BMLT since Day One.
However, the earliest releases were kept in this SVN repository (up to version 1.8.27).
For example, this is the code for the last release of the Version 1.X series (1.10.3) on GitHub.
INSTALLING THE NEW ROOT SERVER
OK. This is one of the really cool things about the new release. Upgrades will be even easier than the 1.Xseries.
UPGRADING FROM 1.X
First of all, I don’t recommend that you just completely replace your root server, unless you are up for a stream of pithy emails from your administrators. The user interface is drastically different from the original.
What I recommend, instead, is that you install the 2.0.0 server in parallel with the 1.X series. This is entirely possible. There are ZERO changes to the database structure (as long as you are using a very current version of the 1.X-series root server).
That way, you can allow your administrators to “train up” on the new server interface. I think they will really like it. It will make their jobs much easier. However, addicts don’t react well to change; even when it is for the best.
Here’s a step-by-step guide to installing the 2.0.0 server as a parallel (second option) interface to the same database as the 1.Xversion server:
- You must be able to download files onto your computer (A Web browser is usually all you need for this).
- You must be able to upload directories to your Web hosting server’s HTTP directory (usually called ‘html’ or ‘public_html’ on most Web hosting sites). In particular, you need read/write access to the directory on your Web server that has your current BMLT root server.
That’s pretty much it.
One thing that I should mention: I will be using ‘main_server’ as the name of the current BMLT root server directory. It is possible to rename this directory, and some installations that I know of have done this. However, when I say ‘main_server’, I mean the top-level directory of the root server.
Another thing: It is possible that some installations may be done in a manner that makes this technique impossible or impractical. If that is the case, then you may not have any choice but to replace the original server wholesale. In that case, skip to the last section.
STEP ZERO: BACK UP!
It is ALWAYS a good idea to back up your installation. You should already be doing this on a regular basis, but you should back up your main_server directory and your BMLT database before proceeding. There should be no issues, but sometimes, things happen (Like your cat getting tangled in your network cable in the middle of a transfer).
STEP ONE: GET A COPY OF THE ORIGINAL CONFIG FILE
This is the file with the initial server settings. It is called ‘auto-config.inc.php’, and is inside the original ‘main_server’ directory, via this path:
Get a COPY of this file (don’t move it), and place it at the same level as your ‘main_server’ directory.
So your directory should now look like this:
Leave the config file there. The really cool thing about the BMLT Root Server 2.Xversion, is that you simply upgrade by replacing the ‘main_sever’ directory. No more going into the directory and fishing out the config file, then putting it back.
STEP TWO: DOWNLOAD THE NEW VERSION CODE TO YOUR COMPUTER
You get the code from one of the links above (We’ll leave it to you as to which version you want to get, as this technique will also work for version 1.10.3).
Unzip the directory on your computer.
You will now have a directory named ‘main_server’, with all the files for the root server (You may also have some other files, you can ignore these. The only thing that you want is ‘main_server’).
STEP THREE: RENAME THE DIRECTORY
Rename ‘main_server’ to ‘new_main_server’ on your machine.
STEP FOUR: UPLOAD THIS DIRECTORY TO YOUR WEB SERVER
Put the ‘new_main_server’ directory into the same directory as ‘main_server’.
Once this is complete, the directory should look like this:
It is now ready to run. You are done.
In order to run the new root server, simply specify ‘new_main_server’ in your URL, instead of ‘main_server’.
Once you are satisfied that everyone is ready for the switch, you then rename ‘main_server’ to ‘old_main_server’, and ‘new_main_server’ to ‘main_server’. You can choose to keep the old server around, or delete it.