Database Connection Settings

Before you can apply the settings on this page, you must set up a new COMPLETELY EMPTY database, and create a database user that has full user rights on that database.

This install wizard will guide you through the process of creating an initial database, as well as a configuration file. In the final step, we will create a settings file, and initialize an empty database.
The first thing that you need to do, is create a new, EMPTY database, and a database user that has full access to that database. This is usually done via your Web site Control Panel. Once you have created the database, you need to enter the information about that database into the text items on this page.
This is usually "localhost."
Only for multiple root servers sharing a database.
Make this an ugly, difficult password. It has a great deal of power, and you will never need to remember it.

Google Maps API Settings

When saving a meeting, the BMLT Root Server uses the Google Maps API to determine the latitude and longitude for the meeting address. These settings are required to allow the BMLT Root Server to communicate with the Google Maps API.

The "API Key" is a key that you need to register with Google in order to be able to use their mapping service.
You will need to provide a valid API Key in order to create new meetings in the Root Server.
The "Region Bias" is a code that is sent to Google when a location search is done, and can help Google to make sense of ambiguous search queries.

Set Various Global Server Settings

These are a few settings that affect the administration and general configuration of this server. Most server settings are done in the server itself.

The Server Administrator is the main user for the server. It is the only account that can create new users and Service bodies, and is very powerful. You should create a login ID and a non-trivial password for this account. You'll be able to modify the other aspects of the account on the main server, once the database has been set up.
This is the login string for the Server Administrator.
Make sure that this is a non-trivial password! It has a great deal of power! (Also, don't forget it).
There is already an existing database, so you cannot set up a Server Administrator account (One already exists).
These are various settings that affect how the root server behaves and appears.
This will also affect the Server Administrator password, above.
This is an approximation of how many meetings need to be found in the automatic radius selection. More meetings means a bigger radius.
The longer the history, the larger the database will become.
If you select this, a popup menu will appear in the login screen, so administrators can select their language.
If not checked, then all administration must be done via the Root Server login (No apps).
This primarily affects the export to NAWS.
If you select this, site visitors will be able to send emails from meeting records.
Sends copies of these emails to the Service Body Administrator (if they are not the primary recipient).
Sends copies of these emails to all of the relevant Service Body Administrators.
If you have entered the database information, provided a valid Google Maps API Key, and specified the login information for the Server Administrator, then you can initialize the root server here. Remember that the database must be COMPLETELY EMPTY of BMLT Root Server tables for this server (It can have tables for other servers or services).

Initialize the Root Server

NAWS Export Spreadsheet (Optional):

Create the Settings File

The root server was unable to create the settings file for you. Instead, we ask you to create it yourself, via FTP or a control panel file manager, name it "", and paste the following text into the file:

The text in the box below is the PHP source code for the main settings file. You will need to create a file on the server with this text in it. The file is at the same level as the main server directory for the root server.
You also need to make sure that the file permissions are restricted (chmod 0644). This prevents the file from being written, and the root server will not run unless the file has the correct permissions.


The file needs to be placed as /home/brokenguyhh/public_html/bmltroot/, which is where your main_server directory is. After the file has been created and you have put the above text into it, you should execute the following command to make sure that the permissions are correct:

chmod 0644 /home/brokenguyhh/public_html/bmltroot/

Once all this is complete, refresh this page, and you should see the root server login page.