Installation - simark/cococo GitHub Wiki

For now, cococo can only be installed manually. An automated install script may be considered in the future, but there is no immediate plan for it.

Set up the MySQL database

Note: all the MySQL steps can be easily done via a graphical interface such as PHPMyAdmin instead of the command line interface.

Log in to MySQL

Log in to MySQL as root or any other user with administrative rights (user / privileges administration and database creation)

$ mysql -u root -p

Enter the root password when prompted.

Create the database

Of course, you can name the database whatever you want. Skip this step if the database you want to use already exists (for example, with shared hosting). Just be consistent in the next steps.

mysql> CREATE DATABASE cococo;

Assign privileges to a user

Grant all privileges to some user on the cococo database. If the user does not exist, it will be created by the command.

mysql> GRANT ALL ON cococo.* TO cococo@localhost IDENTIFIED BY 'some_password';

Import the database schema

Log out from the MySQL CLI (CTRL-D). Locate the .sql files containing the database schema definition (currently in the _des/sql directory) and import them. Enter the password you gave to the cococo user when prompted.

$ mysql -u cococo -p cococo < cococo3.sql

$ mysql -u cococo -p cococo < sproc.sql

Note: the format of the last commands is $ mysql -u <username> -p <database name> < <file to import>

Install the PHP files

Copy the content of the GIT repository where you want your cococo installation to reside, generally somewhere in your DocumentRoot (refer to your web server documentation). You'll want to allow cococo to override a bunch of stuff in its .htaccess file.

Configure the installation

Copy the be/config.ini.sample to be/config.ini. Adjust the db_user, db_passwd and db_db settings to match the values you used when configuring the database.

Test your installation

Point your browser to the address you configured in your webserver and cross your fingers ! PHP settings defined in .htaccess enable all errors and warnings, so that should help you debug in case it's not working.

⚠️ **GitHub.com Fallback** ⚠️