|
|
|
Installation
Install script
After you have performed all of the previous steps, it is now time to run the install script. To run this script, type in the URL to the script into your web browser such as http://www.yourdomain.com/links/install.php. You will then be greeted with an intro screen which will guide you through the script.
The install script will check to ensure that all of the files are in their correct location, and that their permissions are set correctly. You will not be able to proceed in the installation if the install script is not satisfied with the file structure and permissions.
The following is a brief walk through of the screens, and what is expected. Please note that the installer will check to make sure everything is ok as you progress. If something is incorrect, you will be instructed on what needs to be done to correct the issue before you can proceed.
URL/Path screen:
› URL: This is the web address of where the script is located. Make sure to include a trailing backslash. The install script will make it's best guess of where you are installing, but make sure it is accurate.
Examples: http://www.yourdomain.com/ & http://www.yourdomain.com/links/
› PATH: This is the physical path on the server where the files are located at. If you do not know the correct entry, contact your host. Make sure to include a trailing backslash. The install script will make it's best guess of where you are installing, but make sure it is accurate.
Examples: /domain/public_html/ & /domain/htdocs/links/
User system screen:
› User system: Select which user system you wish to you. If you are running BosDirectory as a standalone, choose BosDev UUS. If you are running BosDirectory as a standalone on a company/school/etc Intranet, choose BosDev UUS Intranet. If you wish to integrate BosDirectory with another product such as vBulletin 3, phpBB 2, etc please choose the correct entry.
Database information screen:
› Database name: The name of the database to store the BosDirectory information.
› Database host: The server host used to connect to the database, normally "localhost".
› Database user: The username of the MySQL user who has access to the database.
› Database password: The password of the user who has access to the database.
› Database prefix: BosDirectory creates tables such as "categories", "links" and more. In order to ensure a unique name, the install script asks you for a prefix. This will rename the tables to something not currently in use such as "bdir3_categories" and "bdir3_links". This ensures no other applications are damaged during the BosDirectory installation.
› UUS Database name: The name of the database which will be used to store user information. If you have another BosDev product which uses the BosDev UUS use that information so that both applications can share information enabling the applications to share usernames/passwords.
› UUS Database host: The server host used to connect to the database, normally "localhost".
› UUS Database user: The username of the user who has access to the database.
› UUS Database password: The password of the user who has access to the database.
(The following is only seen if integrating with a third party application such as vBulletin)
› Integration database name: The name of the database where BosDirectory should get integration information.
› Integration database host: The server host used to connect to the database, normally "localhost".
› Integration database user: The username of the user who has access to the database.
› Integration database password: The password of the user who has access to the database.
› Integration database prefix: Your forum or CMS may prefix database table names, enter that prefix here.
User account/cookie information screen:
› Username: Your desired administrator account username. If you are integrating with another product, the username you enter here MUST EXIST in the other product already.
› Password: Your desired password for the administrator account.
› Email: Your email address for the administrator account.
› Cookie prefix: Cookie names, similar to database table names, may be prefixed with a character string to ensure they are unique. If you are integrating with another product, this prefix MUST MATCH the other application.
› Cookie path: This allows you to limit the scope of the cookie to the installation directory. For a side wide cookie, leave this as a /. If you are integrating with another product, this path MUST MATCH the other application.
› Cookie domain: This sets the domain name (server name) of the cookie. This should be set to .yourdomain.com (notice the leading .) If you are integrating with another product, this domain MUST MATCH the other application.
Installation section menu:
› Uploading files to the server
› Creating a database
› Setting file/directory permissions
› Running the installation script
› Cleaning up
|
|
