GeeklogWiki - User contributions [en]

Main Page

2005-04-06T05:12:02Z

Destr0yr:

[[Image:Logo.gif]]

== Geeklog Documentation ==

This is the main entry for Documentation for the [http://www.geeklog.net Geeklog Portal System]. The current version is 1.3x. The next generation portal is also under development and documentation for it will be posted here as it available.

This documentation is a result of community action. Everyone is invited to sign up and participate. If you see an omission you can fill it in. If you see a mistake, correct it. If you see where things could be better organized, change it. If you have a note about a particular configuration, add it. In other words we need your help to make it better.

Authors note that you can refer to yourself or sign your work by linking to User:Youruserid, the shorthand for this is three tildes. This points initially to nothing but a blank page on which you can enter whatever info you want about yourself. You can also reach this page by clicking on your userid at the top of the page when you are logged in.

#[[Geeklog_1.3x_Documentation]]
#[[Geeklog 2x Documentation]]
#[[PEAR::Auth_Enterprise Documentation]]

Installation Instructions

2004-07-31T23:47:49Z

Destr0yr:

{|
|- 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. '''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. 
<table width=95% border=0 cellspacing=2 cellpadding=4 bgcolor=black>
<tr bgcolor=white>
<td>SPECIAL NOTE: '''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. There is also a script at '''http://yourgeeklogsite/admin/install/check.php''' that can test the permissions for you.</td></tr></table> 
<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. 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. 
<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. 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 '\\'. ''Please read the comments in config.php carefully.'' 
<li>Edit '''lib-common.php''' and change the require_once() at the top to point to the location of your '''config.php''' file. 
<li>Open your browser and navigate to '''http://yourgeeklogsite/admin/install/install.php''' and follow the directions! 
<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). 
<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.
|}

<div style="border: 1px solid #ccc; padding: 2px;">
== Rough Examples ==
=== cPanel Environment with Shell Access ===
Given the instructions above, this is purely an addendum for cPanel (possibly Plesk and other) environments. Follow the instructions above and use the following steps as a reference if you get stuck. Please note, it is this authors opinion that you do not use Fantastico to setup Geeklog as it bastardizes the installation steps listed here and places config.php in your webroot (accessable to anyone).
<ul>
<li>After downloading and extracting the geeklog tarball under your webroot, ie. <tt>/home/yoursite/</tt> you will have a <tt>geeklog-1.3.9sr1</tt> folder. Copy or move the contents of this file to your home directory. 
 
<code>cp -R geeklog-1.3.9sr1/* .</code> 
You may now safely remove the geeklog-1.3.9sr1 folder: 
<code>rm -fr geeklog-1.3.9sr1/</code>
 
</li>
<li>Check with your host to determine if phpSuExec is enabled. If enabled the permissions 755 should suffice. If not, you are required to use 777 for the folders listed in step 3 above.</li>
<li>cPanel normally sets <tt>/home/yourwebsite/public_html/</tt> as your webroot. People can see these files, index.php should live here.</li> <li><tt>/home/yourwebsite/</tt> is under the webroot, files that are not seen by the general public. Folders that live here are backups, logs, plugins, public_html and GeekLog's main config file, config.php.
</li>
</ul>
</div>

Installation Instructions

2004-07-01T15:31:37Z

Destr0yr:

<table>
<tr>
<td valign="top" bgcolor="#aec7e8">INSTALLATION INSTRUCTIONS (new installation)</td>
</tr>
<tr>
<td 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 www:www or nobody:nobody 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. 
 

<table width="95%" border="0" cellspacing="2" cellpadding="4" bgcolor="black">
<tr>
<td bgcolor="white">
SPECIAL NOTE: 
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.
There is also a script at http://yourgeeklogsite/admin/install/check.php that can test the permissions for you.
</td>
</tr>
</table>
 
<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. If you are not familiar with using MySQL, you are urged to get <a href="http://www.phpmyadmin.net/">phpMyAdmin</a> and use it to create a new database. If you have no idea what the previous two sentences mean, contact your sysadmin for help. 
 
<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. 
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 '\\'. 
Please read the comments in config.php carefully. 
 
<li>Edit lib-common.php and change the require_once() at the top to point to the location of your config.php file. 
 
<li>Open your browser and navigate to http://yourgeeklogsite/admin/install/install.php and follow the directions! 
 
<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). 
<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. 
 

</ol>
</td>
</tr>
</table>

Pre-Installation Checklist

2004-07-01T15:27:14Z

Destr0yr:

<table style="font-family: Verdana, Helvetica, Arial, sans-serif;">
<tr>
<td valign="top" bgcolor="#aec7e8">PRE-INSTALLATION CHECKLIST (new installation)</td>
</tr>
<tr>
<td valign="top" bgcolor="#cdeeff">
Before installing Geeklog for the first time, please make sure you have or know the following:
<ol>
<li>A web server running PHP 4.04 or higher
<li>A web server running MySQL, with access to a database or the ability to create a database
<li>The ability to create a new database in MySQL or access to an existing one
<li>A telnet or SSH connection to your web server (although FTP will work). This document will be written assuming you have command line access to your server, but we will note the major differences for FTP users.
<li>The ability to unpack a tarball (file ending in tar.gz)
<li>You know the difference between a path and a URL
<li>You know how to determine your system paths 
 

<table width="95%" border="0" cellspacing="2" cellpadding="4" bgcolor="black">
<tr>
<td bgcolor="white">
<div align="left">
SPECIAL NOTE ABOUT PARSE ERRORS: 
Some users have reported that WinZip corrupts certain files in the Geeklog tarball during decompression which will cause errors during the installation process. You are strongly urged not to use WinZip. Try WinRAR if you must decompress the file locally, or better yet, unpack the file from your server (requires telnet/SSH access).
Parse errors can also be caused by using a WYSIWYG editor on lib-common.php, e.g. Dreamweaver - you should use a "plain text editor".
</div>
</td>
</tr>
</table>
 
</ol>

The following instructions will refer to the <tt>public_html</tt> directory
a lot. Here is what this is all about:

Basically, a Geeklog installation consists of two parts: The part that is
visible "to the world" - which is everything in the public_html directory.
"public_html" is a popular name for the world-accessible directory that can be
found on a webserver ("htdocs" and "www" are other popular names). So if you
have such a directory, just copy everything from Geeklog's public_html
directory into that directory on your webserver. Then you only need to set up
$_CONF['path_html'] (in config.php) to point to that directory.

The other part of Geeklog, which is everything outside the public_html
directory, should not be accessible via a URL since it contains sensitive
information. So you should really put those files and directories outside of
your document root (i.e. outside the web server's public_html, htdocs, or www
directory). Then you only need to set up $_CONF['path'] (again, in config.php)
to point to the place where you put those files and directories.

Separating the install in this way will also ensure that you can access your
Geeklog site directly via a domain name (if you have one), e.g.
http://www.yourdomain.com/, and that you don't need to include "public_html"
in the URL.
</td>
</tr>
</table>