1. Figure out how to open text files as root.
2. navigate to or find /private/etc/httpd/
3. From that directory make a backup copy of “httpd.conf” put it somewhere safe
4. Open “httpd.conf” as root.
5. Look around! This is an interesting file that controls how your apache works. You can learn a lot just by looking.
6. find this line of text: Port 80
7. Now change this to read:
   Port newnumber where “newnumber” is the new port number you have chosen. You need to choose a number that is will not be used by another application or process. I chose 400, though I had no good reason for doing so. Folks with more knowledge than me may understand the rational for choosing certain port numbers.
8. Save your changes
9. Stop and Start “Personal Web Sharing” from the Preferences Panel
10. Good luck!

1. Figure out how to open text files as root.
2. navigate to or find /private/etc/httpd/
3. From that directory make a backup copy of “httpd.conf” put it somewhere safe
4. Open “httpd.conf” as root.
5. Look around! This is an interesting file that controls how your apache installation works. You can learn a lot just by looking.
6. Search for this line: Directory "/Library/Web server/Documents"
7. Now look a few of lines down. Change Options Indexes FollowSymLinks MultiViews to Options All MultiViews
8. Below that change AllowOverride None to AllowOverride All
9. Save the config file. Now do this cd /private/etc/httpd/users/. Now type ls You should see files called “user.conf” with your name substituted for “user”. Open the appropriate .conf file as you learned before.
10. Change Options Indexes FollowSymLinks MultiViews to Options All MultiViews
11. Below that change AllowOverride None to AllowOverride All. Now save the file.
12. Restart apache by using the sharing control panel, in System Preferences.
13. OK! Apache is configured. Now you need to make an encrypted password file.
• Navigate in the terminal to the directory you want your password file to reside. Important!: You must put this file outside the web page directory tree, that is, somewhere other than your Sites directory. Otherwise bad people can just look at this file!
• in the terminal type htpasswd -c .htpasswd yourname which will prompt you for the password. This will create a file called .htpasswd in the directory that you are currently in. If you want to update the file, perhaps adding new usernames, just do the same thing omitting the -c (create) flag
14. Now you need to create a .htaccess file:
• make a new text file called .htaccess.
• put in this text replacing the appropriate parts. “yourpath/.htpasswd” will of course just be the path to the file you created in the last step.
  AuthUserFile /yourpath/.htpasswd
AuthName 'your sitename (or whatever)'
AuthType Basic
require user yourname yourname2 yourname3

• Save in the directory that you wish these restrictions to apply to.
15. You can create additional .htaccess files in any part of your web directory tree. Each will apply to all files and directories under it unless another .htaccess file is there.
16. Done! Go crazy.

1. Figure out how to open text files as root.
2. navigate to or find /private/etc/httpd/
3. From that directory make a backup copy of “httpd.conf” put it somewhere safe
4. Look around! This is an interesting file that controls how your apache works. You can learn a lot just by looking.
5. find these two lines of text:
• LoadModule php4_module
• AddModule mod_php4.c
6. Remove the “#” sign from in front of each line. This “uncomments” it, making it readable by apache. Save your changes.
7. Find the following text:

   # AddType allows you to tweak mime.types without actually editing it, or to

   # make certain files to be certain types.

   and replace it with:

   # AddType allows you to tweak mime.types without actually editing it, or to
# make certain files to be certain types.
For PHP 4.x, use:
AddType application/x-httpd-php .php


8. Restart apache by using the sharing control panel, or typing sudo apachectl restart (thats an “L” at the end of “apachectl” not a numeral “1″
9. Create a web page called test.php or whatever, and put in this in the body of your page: <?php phpinfo(); ?>.
10. view this page in a browser. Make sure you are not looking at the local file, but at the page using your internet address, as if you were an outside visitor. This will show you all sorts of cool stuff about your configuration, and confirm that php is working.
11. Good Luck!

There are a number of ways to edit files as root.

• login as root at the OS X login screen (if enabled), then open as usual. This method is not recommended
• in the terminal open as root in pico by typing sudo pico path/filename
• in the terminal open as root in Textedit by typing sudo open -a /Applications/TextEdit.app/ path/filename
• open using a program like bbedit (powerful!) or textwrangler (free!) that simply ask for a password should you need root privilages to save a file. This is probably the easiest way.

Lets get the terminology straight. For the purposes of this discussion, we will call the machine you want to login to the “server”. The machine you are logging in from (without a password) is the “client”.

In order for this to work you must have an account on both machines. Be sure to work on the accounts that you will be loging in to and from respectively.

1. On the client: ssh-keygen -t dsa
2. hit “enter” to accept the default file location
3. hit “enter” twice to proceed without a password
4. Take note of where your public key was saved, then go there
5. Copy the contents of id_dsa.pub
6. On the server cd ~/.ssh/
7. Open the file called “authorized_keys” (create it if necessary)
8. Paste the contents of id_dsa.pub into this file, then save the file
9. Done! You should be able to login via ssh from the client to the server without a password

Gotchas and discussion:

• dsa seems to be a solid choice for encryption type, over for instance, rsa. However, I’m not an expert, so you should satisfy yourself as to the right choice
• The whole point of this is to avoid having to enter a password, so I don’t enter a password to protect my keys. Only do this if you feel confident that your private key will be safely under your control.
• I used “copy” and “paste” in my instructions to try to cater to the less experienced users. If you would rather do things like cat id_dsa.pub >> ~/.ssh/authorized_keys then go for it.
• Make sure you don’t introduce return characters (line breaks) into authorized_keys by mistake. The whole key is supposed to be two lines, like this:
  ssh-dss
AAAAB3NzaC1kc3MA ..............(lots more)

Monsters were taking over the earth. Regular people and animals were morphing into scary blank faced things. Even birds were turning into little flopping balls a jelly-plasticky-yuck. I and my anonymous sidekick retreated to a cave where I thought we would be safe. We mostly were until one of the plasticky globule bird things flew down into the cave with us. I cut it in half with a sword as it flew at us, just like Uma Thurman in “Kill Bill” did to the baseball. My sidekick knelt down to look at the half of the thing that looked like a fluffy pile of saran wrap, when suddenly it went for her (sidekick had now resolved into a “she”) face alien style. It stretched a thin sheet of plastic-like wrap across her mouth and nose so she couldn’t breath. I ran to pull it off, but it was amazingly strong. I tried to puncture it with my fingers but I couldn’t. So with her mouth wide open, as she continued to try to breath I used a pocket knife puncture the plastic, which was still very tough, then slowly pulled a hole open with my fingers. But another layer had formed in the front of her mouth, and I could see another forming at the back of her mouth. So trying to work quickly without cutting her, I managed to puncture and open a breathing hole in the next two layers. Once she was able to breath, I was able to pull the plastic stuff away. So the lesson is, be careful with that plastic wrap.

1. # emerge awstats
2. Create a directory called “awstats” in your root web directory.
3. #webapp-config -I -h localhost -d /awstats/ awstats 6.3-r2 Change version number as necessary.
4. Take the output of the above command and paste into the /etc/apache2/conf/commonapache2.conf file
5. # /etc/init.d/apache2 restart
6. # cd /etc/awstats/
7. If there isn’t already a config file, copy awstats.model.conf to awstats.yourdomain.conf
8. Edit awstats.yourdomain.conf. It is pretty easy just reading the comments.

OK it is installed. Now update the stats:
#/usr/share/webapps/awstats/6.3-r2/hostroot/cgi-bin/awstats.pl -config=yourdomain.com -update

I put this in my cronfile so that it updates every night:
30 02 * * * /usr/share/webapps/awstats/6.3-r2/hostroot/cgi-bin/awstats.pl -config=aliandcedar.com -update >> /var/log/awstats/awstats.log 2>&1
That worked for me.