Difference between revisions of "Installation Instructions"

From GeeklogWiki
Jump to: navigation, search
(spam, reverting)
Line 10: Line 10:
 
|- valign=top bgcolor=#cdeeff
 
|- valign=top bgcolor=#cdeeff
 
|Please read this section '''COMPLETELY''' before beginning.
 
|Please read this section '''COMPLETELY''' before beginning.
<ol>
+
<ol>
&lt;li&gt;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):
+
<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):
  
;&lt;code&gt;tar -zxvf geeklog-1.3.9sr1.tar.gz&lt;/code&gt;
+
;<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.
 
;'''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.
  
&lt;li&gt;For *nix installations the following may be required:
+
<li>For *nix installations the following may be required:
  
;&lt;code&gt;chown -R ''webuser'':''webuser'' /path/to/geeklog&lt;/code&gt;
+
;<code>chown -R ''webuser'':''webuser'' /path/to/geeklog</code>
  
;This guarantees that everything in that path belongs to you, typical settings are &lt;nowiki&gt;www:www&lt;/nowiki&gt; or &lt;nowiki&gt;nobody:nobody&lt;/nowiki&gt; and more often than not doesn't matter.
+
;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.
  
&lt;li&gt;For *nix installations cd into /path/to/geeklog and do the following:
+
<li>For *nix installations cd into /path/to/geeklog and do the following:
  
;&lt;code&gt;chmod -R 775 logs/
+
;<code>chmod -R 775 logs/
 
;chmod -R 775 public_html/backend/
 
;chmod -R 775 public_html/backend/
 
;chmod -R 775 public_html/images/articles
 
;chmod -R 775 public_html/images/articles
;chmod -R 775 public_html/images/userphotos&lt;/code&gt;
+
;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.&lt;br&gt;'''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.&lt;br&gt;&lt;br&gt;
+
;'''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>
&lt;table width=95% border=0 cellspacing=2 cellpadding=4 bgcolor=black&gt;
+
<table width=95% border=0 cellspacing=2 cellpadding=4 bgcolor=black>
&lt;tr bgcolor=white&gt;
+
<tr bgcolor=white>
&lt;td&gt;&lt;font color=&quot;#FF0000&quot;&gt;SPECIAL NOTE: &lt;/font&gt;&lt;br&gt;&lt;br&gt;'''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.&lt;br&gt;&lt;br&gt;There is also a script at '''http://yourgeeklogsite/admin/install/check.php''' that can test the permissions for you.&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;&lt;br&gt;
+
<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>
&lt;li&gt;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.&lt;br&gt;&lt;br&gt;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.&lt;br&gt;&lt;br&gt;
+
<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>
&lt;li&gt;Edit config.php with the appropriate settings for your server. For installation, this basically means &quot;set your paths,&quot; as all other variables can be changed after a successful installation. The config.php file contains comments to help you out.&lt;br&gt;&lt;br&gt;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 '\\'.&lt;br&gt;&lt;br&gt;''Please read the comments in config.php carefully.''&lt;br&gt;&lt;br&gt;
+
<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>
&lt;li&gt;Edit '''lib-common.php''' and change the require_once() at the top to point to the location of your '''config.php''' file.&lt;br&gt;&lt;br&gt;
+
<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>
&lt;li&gt;Open your browser and navigate to '''http://yourgeeklogsite/admin/install/install.php''' and follow the directions!&lt;br&gt;&lt;br&gt;
+
<li>Open your browser and navigate to '''http://yourgeeklogsite/admin/install/install.php''' and follow the directions!<br><br>
&lt;li&gt;Once you see the success message, you are ready to go. '''You can now delete the admin/install directory''' (and all files within it).&lt;br&gt;&lt;br&gt;
+
<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>
&lt;li&gt;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.
+
<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.
 
|}
 
|}
  
&lt;div style=&quot;border: 1px solid #ccc; padding: 2px;&quot;&gt;
+
<div style="border: 1px solid #ccc; padding: 2px;">
  
 
== Rough Examples ==
 
== Rough Examples ==
 
=== cPanel Environment with Shell Access ===
 
=== 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).
 
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).
&lt;ul&gt;
+
<ul>
&lt;li&gt;After downloading and extracting the geeklog tarball under your webroot, ie. &lt;tt&gt;/home/yoursite/&lt;/tt&gt; you will have a &lt;tt&gt;geeklog-1.3.9sr1&lt;/tt&gt; folder.  Copy or move the contents of this file to your home directory.&lt;br /&gt;
+
<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.<br />
&lt;br /&gt;
+
<br />
&lt;code&gt;cp -R geeklog-1.3.9sr1/* .&lt;/code&gt;&lt;br /&gt;&lt;Br /&gt;
+
<code>cp -R geeklog-1.3.9sr1/* .</code><br /><Br />
You may now safely remove the geeklog-1.3.9sr1 folder:&lt;br /&gt;&lt;br /&gt;
+
You may now safely remove the geeklog-1.3.9sr1 folder:<br /><br />
&lt;code&gt;rm -fr geeklog-1.3.9sr1/&lt;/code&gt;
+
<code>rm -fr geeklog-1.3.9sr1/</code>
&lt;br /&gt;&lt;br /&gt;
+
<br /><br />
&lt;/li&gt;
+
</li>
&lt;li&gt;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.&lt;/li&gt;
+
<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>
&lt;li&gt;cPanel normally sets &lt;tt&gt;/home/yourwebsite/public_html/&lt;/tt&gt; as your webroot.  People can &lt;b&gt;see&lt;/b&gt; these files, index.php should live here.&lt;/li&gt; &lt;li&gt;&lt;tt&gt;/home/yourwebsite/&lt;/tt&gt; is under the webroot, files that are &lt;b&gt;not seen&lt;/b&gt; by the general public.  Folders that live here are backups, logs, plugins, public_html and GeekLog's main config file, config.php.
+
<li>cPanel normally sets <tt>/home/yourwebsite/public_html/</tt> as your webroot.  People can <b>see</b> these files, index.php should live here.</li> <li><tt>/home/yourwebsite/</tt> is under the webroot, files that are <b>not seen</b> by the general public.  Folders that live here are backups, logs, plugins, public_html and GeekLog's main config file, config.php.
&lt;/li&gt;
+
</li>
&lt;/ul&gt;
+
</ul>
&lt;/div&gt;
+
</div>
  
&lt;div style=&quot;border: 1px solid #ccc; padding: 12px;&quot;&gt;
+
<div style="border: 1px solid #ccc; padding: 12px;">
 
Another Geeklog user has prepared written install instructions and posted it here: [http://www.edplans.com/tech/computers/geeklogInstall.php]
 
Another Geeklog user has prepared written install instructions and posted it here: [http://www.edplans.com/tech/computers/geeklogInstall.php]
&lt;/div&gt;
+
</div>
[http://acyclovir.1.p2l.info 0] [http://adipex.1.p2l.info 1] [http://allegra.1.p2l.info 2] [http://allergy.1.p2l.info 3] [http://ambien.1.p2l.info 4] [http://antidepressants.1.p2l.info 5] [http://anxiety.1.p2l.info 6] [http://birth-control.1.p2l.info 7] [http://bontril.1.p2l.info 8] [http://bupropion-hcl.1.p2l.info 9] [http://buspar.1.p2l.info 10] [http://buspirone.1.p2l.info 11] [http://butalbital-apap.1.p2l.info 12] [http://carisoprodol.1.p2l.info 13] [http://celebrex.1.p2l.info 14] [http://celexa.1.p2l.info 15] [http://cialis.1.p2l.info 16] [http://cyclobenzaprine.1.p2l.info 17] [http://didrex.1.p2l.info 18] [http://effexor-xr.1.p2l.info 19] [http://enpresse.1.p2l.info 20] [http://esgic.1.p2l.info 21] [http://famvir.1.p2l.info 22] [http://female-v.1.p2l.info 23] [http://fioricet.1.p2l.info 24] [http://flexeril.1.p2l.info 25] [http://flextra.1.p2l.info 26] [http://flonase.1.p2l.info 27] [http://fluoxetine.1.p2l.info 28] [http://gastrointestinal.1.p2l.info 29] [http://herpes.1.p2l.info 30] [http://imitrex.1.p2l.info 31] [http://ionamin.1.p2l.info 32] [http://levitra.1.p2l.info 33] [http://lexapro.1.p2l.info 34] [http://loestrin.1.p2l.info 35] [http://mens.1.p2l.info 36] [http://meridia.1.p2l.info 37] [http://muscle-relaxers.1.p2l.info 38] [http://nasacort.1.p2l.info 39] [http://nasonex.1.p2l.info 40] [http://nexium.1.p2l.info 41] [http://nordette.1.p2l.info 42] [http://ortho-tri-cyclen.1.p2l.info 43] [http://pain-relief.1.p2l.info 44] [http://paxil.1.p2l.info 45] [http://phendimetrazine.1.p2l.info 46] [http://phentermine.1.p2l.info 47] [http://prevacid.1.p2l.info 48] [http://prilosec.1.p2l.info 49] [http://propecia.1.p2l.info 50] [http://renova.1.p2l.info 51] [http://retin-a.1.p2l.info 52] [http://seasonale.1.p2l.info 53] [http://skelaxin.1.p2l.info 54] [http://skin-care.1.p2l.info 55] [http://sleep-aids.1.p2l.info 56] [http://soma.1.p2l.info 57] [http://sonata.1.p2l.info 58] [http://stop-smoking.1.p2l.info 59] [http://supplements.1.p2l.info 60] [http://tenuate.1.p2l.info 61] [http://tizanidine.1.p2l.info 62] [http://tramadol.1.p2l.info 63] [http://triphasil.1.p2l.info 64] [http://ultracet.1.p2l.info 65] [http://ultram.1.p2l.info 66] [http://valtrex.1.p2l.info 67] [http://vaniqa.1.p2l.info 68] [http://viagra.1.p2l.info 69] [http://viagra-soft-tabs.1.p2l.info 70] [http://vioxx.1.p2l.info 71] [http://vitalitymax.1.p2l.info 72] [http://weight-loss.1.p2l.info 73] [http://wellbutrin.1.p2l.info 74] [http://xenical.1.p2l.info 75] [http://yasmin.1.p2l.info 76] [http://zanaflex.1.p2l.info 77] [http://zebutal.1.p2l.info 78] [http://zoloft.1.p2l.info 79] [http://zyban.1.p2l.info 80] [http://zyrtec.1.p2l.info 81] [http://adipex.3.p2l.info 82] [http://ambien.3.p2l.info 83] [http://celexa.3.p2l.info 84] [http://cialis.3.p2l.info 85] [http://fioricet.3.p2l.info 86] [http://flonase.3.p2l.info 87] [http://herpes.3.p2l.info 88] [http://imitrex.3.p2l.info 89] [http://levitra.3.p2l.info 90] [http://lexapro.3.p2l.info 91] [http://meridia.3.p2l.info 92] [http://nordette.3.p2l.info 93] [http://phentermine.3.p2l.info 94] [http://skelaxin.3.p2l.info 95] [http://tramadol.3.p2l.info 96] [http://triphasil.3.p2l.info 97] [http://valtrex.3.p2l.info 98] [http://viagra.3.p2l.info 99] [http://weight-loss.3.p2l.info 100] [http://wellbutrin.3.p2l.info 101] [http://xenical.3.p2l.info 102] [http://yasmin.3.p2l.info 103] [http://zoloft.3.p2l.info 104] [http://zyrtec.3.p2l.info 105] [http://adipex.4.p2l.info 106] [http://ambien.4.p2l.info 107] [http://celexa.4.p2l.info 108] [http://cialis.4.p2l.info 109] [http://fioricet.4.p2l.info 110] [http://flonase.4.p2l.info 111] [http://herpes.4.p2l.info 112] [http://imitrex.4.p2l.info 113] [http://levitra.4.p2l.info 114] [http://lexapro.4.p2l.info 115] [http://meridia.4.p2l.info 116] [http://nordette.4.p2l.info 117] [http://phentermine.4.p2l.info 118] [http://skelaxin.4.p2l.info 119] [http://tramadol.4.p2l.info 120] [http://triphasil.4.p2l.info 121] [http://valtrex.4.p2l.info 122] [http://viagra.4.p2l.info 123] [http://weight-loss.4.p2l.info 124] [http://wellbutrin.4.p2l.info 125] [http://xenical.4.p2l.info 126] [http://yasmin.4.p2l.info 127] [http://zoloft.4.p2l.info 128] [http://zyrtec.4.p2l.info 129] [http://ab.5.p2l.info 130] [http://ak.5.p2l.info 131] [http://al.5.p2l.info 132] [http://ar.5.p2l.info 133] [http://as.5.p2l.info 134] [http://az.5.p2l.info 135] [http://bc.5.p2l.info 136] [http://ca.5.p2l.info 137] [http://co.5.p2l.info 138] [http://ct.5.p2l.info 139] [http://dc.5.p2l.info 140] [http://de.5.p2l.info 141] [http://def.5.p2l.info 142] [http://fl.5.p2l.info 143] [http://ga.5.p2l.info 144] [http://gu.5.p2l.info 145] [http://hi.5.p2l.info 146] [http://ia.5.p2l.info 147] [http://id.5.p2l.info 148] [http://il.5.p2l.info 149] [http://in.5.p2l.info 150] [http://ks.5.p2l.info 151] [http://ky.5.p2l.info 152] [http://la.5.p2l.info 153] [http://ma.5.p2l.info 154] [http://mb.5.p2l.info 155] [http://md.5.p2l.info 156] [http://me.5.p2l.info 157] [http://mi.5.p2l.info 158] [http://mn.5.p2l.info 159] [http://mo.5.p2l.info 160] [http://mp.5.p2l.info 161] [http://ms.5.p2l.info 162] [http://mt.5.p2l.info 163] [http://nb.5.p2l.info 164] [http://nc.5.p2l.info 165] [http://nd.5.p2l.info 166] [http://ne.5.p2l.info 167] [http://nf.5.p2l.info 168] [http://nh.5.p2l.info 169] [http://nj.5.p2l.info 170] [http://nm.5.p2l.info 171] [http://ns.5.p2l.info 172] [http://nv.5.p2l.info 173] [http://ny.5.p2l.info 174] [http://oh.5.p2l.info 175] [http://ok.5.p2l.info 176] [http://on.5.p2l.info 177] [http://or.5.p2l.info 178] [http://pa.5.p2l.info 179] [http://pe.5.p2l.info 180] [http://pr.5.p2l.info 181] [http://qc.5.p2l.info 182] [http://ri.5.p2l.info 183] [http://sc.5.p2l.info 184] [http://sd.5.p2l.info 185] [http://sk.5.p2l.info 186] [http://tn.5.p2l.info 187] [http://tx.5.p2l.info 188] [http://ut.5.p2l.info 189] [http://va.5.p2l.info 190] [http://vi.5.p2l.info 191] [http://vt.5.p2l.info 192] [http://wa.5.p2l.info 193] [http://wi.5.p2l.info 194] [http://wv.5.p2l.info 195] [http://wy.5.p2l.info 196] [http://yt.5.p2l.info 197]
 

Revision as of 01:17, 25 May 2005

visual overview

The following graphic is an overview of the geeklog installation and directory structure. You should read and review the detailed installation steps starting with the pre-installation checklist but this illustration will be helpfull in orienting you and in providing some quick tips. GeeklogInstallOverview.jpg


INSTALLATION INSTRUCTIONS (new installation)
Please read this section COMPLETELY before beginning.
  1. 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):
    tar -zxvf geeklog-1.3.9sr1.tar.gz
    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.
  2. For *nix installations the following may be required:
    chown -R webuser:webuser /path/to/geeklog
    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.
  3. For *nix installations cd into /path/to/geeklog and do the following:
    chmod -R 775 logs/
    chmod -R 775 public_html/backend/
    chmod -R 775 public_html/images/articles
    chmod -R 775 public_html/images/userphotos
    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.

    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.

  4. 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 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.

  5. 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.

  6. Edit lib-common.php and change the require_once() at the top to point to the location of your config.php file.

  7. Open your browser and navigate to http://yourgeeklogsite/admin/install/install.php and follow the directions!

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

  9. 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.

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).

  • After downloading and extracting the geeklog tarball under your webroot, ie. /home/yoursite/ you will have a geeklog-1.3.9sr1 folder. Copy or move the contents of this file to your home directory.

    cp -R geeklog-1.3.9sr1/* .

    You may now safely remove the geeklog-1.3.9sr1 folder:

    rm -fr geeklog-1.3.9sr1/

  • 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.
  • cPanel normally sets /home/yourwebsite/public_html/ as your webroot. People can see these files, index.php should live here.
  • /home/yourwebsite/ 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.

Another Geeklog user has prepared written install instructions and posted it here: [1]