Difference between revisions of "Installation Instructions"

|- valign=top bgcolor=#aec7e8

|'''INSTALLATION INSTRUCTIONS (new installation)'''

|- valign=top bgcolor=#cdeeff

|Please read this section '''COMPLETELY''' before beginning.

<ol>

<li>Unpack the tarball *within* your web tree by running the following in your shell (this assumes you have ssh access and that you are working with the tarball ''on the designated server''- this can be locally or hosted elsewhere):

 

;<code>tar -zxvf geeklog-1.3.9sr1.tar.gz</code>

 

;'''FTP, Windows Users:''' unpack the tarball on your ''local computer'' and upload the result to your designated server. Everything uploads as ASCII except the images.

 

<li>For *nix installations the following may be required:

 

;<code>chown -R ''webuser'':''webuser'' /path/to/geeklog</code>

 

;This guarantees that everything in that path belongs to you, typical settings are <nowiki>www:www</nowiki> or <nowiki>nobody:nobody</nowiki> and more often than not doesn't matter.

 

<li>For *nix installations cd into /path/to/geeklog and do the following:

 

;<code>chmod -R 775 logs/

;chmod -R 775 public_html/backend/

;chmod -R 775 public_html/images/articles

;chmod -R 775 public_html/images/userphotos</code>

 

;'''FTP Users:''' If you're doing the chmod via a FTP client, you must also apply the chmod to the files in logs/ and public_html/backend as well as the directories themselves. Most, if not all, ftp clients do not perform this command recursively.  That means you need to set each file within each of these directories manually.<br>'''NOTE:''' Some hostings do not allow you to write logs to logs folder outside of the webfolder (aka public_html) or they may already have there their own folder logs/ with strict permissions, for those or similar reasons you have to change the path to logs. For example, put it under public_html, within your web root. If so, change $_CONF path_log for your new path, make or move logs folder with both files there and make sure permissions are set at new place.<br><br>

<table width=95% border=0 cellspacing=2 cellpadding=4 bgcolor=black>

<tr bgcolor=white>

<td><font color="#FF0000">SPECIAL NOTE: </font><br><br>'''Not following step #3 correctly is the #1 reason why people receive errors when they first try to use Geeklog'''. Take your time and get it right. Also, some users have reported problems if the above permissions are not set to 777. Try 775 first and only be more permissive if you receive an error message.<br><br>There is also a script at '''http://yourgeeklogsite/admin/install/check.php''' that can test the permissions for you.</td></tr></table><br>

<li>Create the database you want Geeklog to reside in. You only need to create an empty database - the install script (see below) will create the tables for you.<br><br>If you are not familiar with using MySQL, you are urged to get [http://www.phpmyadmin.net phpMyAdmin] and use it to create a new database. If you have no idea what the previous two sentences mean, contact your sysadmin for help.<br><br>

<li>Edit config.php with the appropriate settings for your server. For installation, this basically means "set your paths," as all other variables can be changed after a successful installation. The config.php file contains comments to help you out.<br><br>Windows users, you should be able to use the Unix '/' in your paths without any problems. Otherwise, you will need to use the doubled Windows slashes '\\'.<br><br>''Please read the comments in config.php carefully.''<br><br>

<li>Edit '''lib-common.php''' and change the require_once() at the top to point to the location of your '''config.php''' file.<br><br>

<li>Open your browser and navigate to '''http://yourgeeklogsite/admin/install/install.php''' and follow the directions!<br><br>

<li>Once you see the success message, you are ready to go. '''You can now delete the admin/install directory''' (and all files within it).<br><br>

<li>Read the first story on your Geeklog site to learn how to log in as the administrator. Please remember to change the default passwords on all pre-configured accounts right away.