Geeklog Forums

What is a *nix installation? Are steps 2 and 3 SSH commands that I need to use, if so can you explain the rest of the installation in newbie terms or is there a document out there that serves this function? LOL

Any operating system that ends in ...nix 8)

You may also want to try Alternative installation instructions

bye, Dirk

what is a webroot? I have dreamhost and the file structure for my site is /yourdomain.net, at least that's what it says. So I install the geeklog file under the /yourdomain.net directory or the / directory?

Webroot / document root means the directory that maps to the base URL of your site.

So if your site is at www.example.com and you have a file foo.php that should be accessible as www.example.com/foo.php, then you have to put foo.php into your webroot.

The graphic in the wiki (linked from the above-mentioned FAQ entry) should help here, I'd hope.

bye, Dirk

i'm cool now, the graphic is a better description visual but i still could not tell what a webroot is. now i do thank you.

in step 2, is this command SSH and I'm assuming webuser is my account, for instance john56, so the command line would be:

chown -R john56
john56 /path/to/geeklog

and that path would be something like this instead: /yoursite.com/geeklog folder?

in step 3, i would cd into /yoursite/geeklog folder and the SSH commands would be:

chmod -R 775 logs/
chmod -R 775 public_html/backend/
chmod -R 775 public_html/images/articles
chmod -R 775 public_html/images/userphotos

?

please read the following post, i edited and i didn't know if the post sends out a replied email if the post was edited. this is off-track, but what is the difference between a silent edit and just an edit? LOL

Sorry ahead to bump this up guys but has anyone installed this on a shared server yet?

Whenever you've signed up with a Internet service provider (ISP), you probably get some space on a particular server (a computer). Such computer works with files and stores them in directories. That's called a filesystem. These directories can be visualised as a tree.

Your space is located somewhere in a specific directory. Whenever you login into your ISP (using telnet, SSH, Putty or kermit ), your login starts in that particular directory. That particular directory is called your home directory. Some systems tend to hide the real name and show you only '/'.

Traditionally that directory is pre-formatted with a sub-directory (a directory within that directory) that bears the name 'public_html' or 'www'. Some systems hide this name too and show you '/your-domain' (as an example) or your name or account.

These computers run software too, and one of these software is f.i. Apache, the web server software. This software is configured to look in specific directories to find webpages. The system admin of your ISP maps your domain to your home directory's sub-directory 'public_html' (or 'www'.
This means that your files in that subdirectory can be retrieved by Apache.
It is called the webroot or the private htdocs.
This means also that your files in your home directory are NOT accessible by Apache.
That technique is talked about with the phrase 'keep your files private', which means that you do not put your private files in the 'www' or 'public_html' sub-directory.

Now, if you've picked a ISP that only makes available a webroot directory, than you cannot store private files and keep them private at the same time.
A substantial part of geeklog needs to be kept private, so you have to decide in this case to expose this part to Apache as well, or pick a different ISP.

Hope this helps.