/conf/_basic_config.php is b2evolution’s main config file.
This file is created during the installation process, using the file
/conf/_basic_config.template.php as a model.
If you wish, you can also duplicate/rename this file manually and enter correct settings before running the installation script.
$baseurl = 'http://www.yourdomain.com/optional_directory/';
$baseurl is where your blogs reside by default. CHECK THIS CAREFULLY or nothing will work.
It should be set to the URL where you can find the blog templates and/or the blog stub files, that means index.php, blog1.php, blog2.php, etc. as well as admin.php.
Note: Blogs can be in subdirectories of the baseurl. However, no blog should be outside of there, or some tricky things may fail (including intempestive logouts)
IMPORTANT: If you want to test b2evolution on your local machine, do NOT use that machine’s name in the $baseurl!
For example, if your machine is called HOMER, do not use
http://localhost/b2evolution/ instead. And log in on localhost too, not homer!
If you don’t, login cookies will not hold.
$db_config = array( 'user' => 'username', // your MySQL username 'password' => 'pass', // ...and password 'name' => 'database_name', // the name of the database 'host' => 'localhost', // MySQL Server (typically 'localhost') );
MySQL DB settings.
Fill in your database details (check carefully or nothing will work!)
The tables prefix (gets placed before each b2evo table name)
$tableprefix = 'evo_';
Use this to have multiple installations in one single database.
Allow DB Reset
If you want to be able to reset your existing b2evolution tables and start anew you must set
$allow_evodb_reset to 1.
$allow_evodb_reset = 0;
This will enable a new option in the installer menu and will allow you to reset your database.
NEVER LEAVE THIS SETTING ON ANYTHING ELSE THAN 0 (ZERO) ON A PRODUCTION SERVER. IF THIS IS ON (1) AND YOU FORGET TO DELETE THE INSTALL FOLDER, ANYONE WOULD BE ABLE TO ERASE YOUR B2EVOLUTION TABLES AND DATA WITH A SINGLE CLICK!
$maintenance_mode = 0;
Set this to 1 Set this to 1 in order to temporarily disable access to the application.
Note: it is still possible to access the install script during maintenance mode.
Note: there is a better and easier way to do this by renaming the _maintenance.html file.