From: Carsten K. <car...@us...> - 2002-01-01 22:57:37
|
Update of /cvsroot/phpwiki/phpwiki/doc In directory usw-pr-cvs1:/tmp/cvs-serv12855 Modified Files: INSTALL.MacOSX Log Message: Fxed typo in "nice" url example, added theme info to Apache alias settings. Minor text reformatting. Index: INSTALL.MacOSX =================================================================== RCS file: /cvsroot/phpwiki/phpwiki/doc/INSTALL.MacOSX,v retrieving revision 1.11 retrieving revision 1.12 diff -C2 -r1.11 -r1.12 *** INSTALL.MacOSX 2001/12/31 01:46:04 1.11 --- INSTALL.MacOSX 2002/01/01 22:57:34 1.12 *************** *** 24,32 **** customizing PhpWiki, working with PHP or doing any other code development. Among other niceties it provides multiple undos (even ! beyond the last file save), line numbering and syntax coloring; but ! don't rely on PB's text colors too much, it doesn't always properly ! handle coloring for \"escaped quotes\" which are frequently called for ! in PHP when generating HTML code. ! \\" <--(kludge for broken syntax coloring) Instructions for using Project Builder with PhpWiki can be found at --- 24,31 ---- customizing PhpWiki, working with PHP or doing any other code development. Among other niceties it provides multiple undos (even ! beyond the last file save), line numbering and syntax coloring; ! however it doesn't always properly handle coloring for strangely ! nested \"escaped quotes\" which are frequently called for in PHP when ! generating HTML code. \\" <--(kludge for broken syntax coloring) Instructions for using Project Builder with PhpWiki can be found at *************** *** 87,91 **** want to compile these programs for yourself. ! <http://www.entropy.ch/software/macosx/> Note that whether you use the built-in PHP module or another PHP --- 86,90 ---- want to compile these programs for yourself. ! <http://www.entropy.ch/software/macosx/> Note that whether you use the built-in PHP module or another PHP *************** *** 97,101 **** can be used with Mac OS X are listed at: ! <http://versiontracker.com/macosx/> --- 96,100 ---- can be used with Mac OS X are listed at: ! <http://versiontracker.com/macosx/> *************** *** 107,120 **** warnings about a depreciated user function with each page load. ! 1. Move the current contents of '/System/Library/PHP' into a backup ! folder, such as '/System/Library/PHP/PEAR-4.0.6'. ! 2. Take the contents of the 'pear' folder from the official PHP 4.1 ! tarball (php-4.1.0.tar.gz) and move it into '/System/Library/PHP'. A precompiled PHP 4.1 module for Apache and the PearDB support files are also available at: ! <http://homepage.mac.com/carstenklapp/> --- 106,119 ---- warnings about a depreciated user function with each page load. ! 1. Move the current contents of '/System/Library/PHP' into a backup ! folder, such as '/System/Library/PHP/PEAR-4.0.6'. ! 2. Take the contents of the 'pear' folder from the official PHP 4.1 ! tarball (php-4.1.0.tar.gz) and move it into '/System/Library/PHP'. A precompiled PHP 4.1 module for Apache and the PearDB support files are also available at: ! <http://homepage.mac.com/carstenklapp/> *************** *** 130,137 **** but with the changes to sections 1 and 2 listed below. ! 1. The Mac OS X Apache web server runs as user "www" and this works ! fine with PhpWiki so long as "Everyone" has at least read-only ! access in the phpwiki folder's Get Info. If you want to perform serial dumps instead of ZIP dumps you need to set at least one directory to be accessible read-write by the http --- 129,138 ---- but with the changes to sections 1 and 2 listed below. ! Section 1 + The Mac OS X Apache web server runs as user "www" and this works fine + with PhpWiki so long as "Everyone" has at least read-only access in + the phpwiki folder's Get Info. + If you want to perform serial dumps instead of ZIP dumps you need to set at least one directory to be accessible read-write by the http *************** *** 142,150 **** sudo chown www:www /System/Library/phpwiki/dumps sudo chmod u+wrx /System/Library/phpwiki/dumps ! 2. A few lines need to be inserted into Apache's configuration in ! order to use "nice" URLs with PhpWiki such as: ! http://somehost/wiki?GoodStyle Open the terminal and type in the following to edit the web server --- 143,153 ---- sudo chown www:www /System/Library/phpwiki/dumps sudo chmod u+wrx /System/Library/phpwiki/dumps + + Section 2 ! A few lines need to be inserted into Apache's configuration in order ! to use "nice" URLs with PhpWiki such as: ! "http://somehost/wiki/GoodStyle" Open the terminal and type in the following to edit the web server *************** *** 171,174 **** --- 174,179 ---- Alias /wiki/images/ "/Library/WebServer/Documents/phpwiki/images/" Alias /wiki/images "/Library/WebServer/Documents/phpwiki/images" + Alias /wiki/themes/ "/Library/WebServer/Documents/phpwiki/themes/" + Alias /wiki/themes "/Library/WebServer/Documents/phpwiki/themes" Alias /wiki/ "/Library/WebServer/Documents/phpwiki/index.php/" Alias /wiki "/Library/WebServer/Documents/phpwiki/index.php" *************** *** 190,198 **** define('VIRTUAL_PATH', '/wiki'); ! 3. To retain your PhpWiki logs between system restarts you should ! specify a non-temporary directory. I recommend you use the same ! folder where the web-server stores it's logs. Change the following ! (line 73) in index.php from: define('ACCESS_LOG', '/tmp/wiki_access_log'); --- 195,205 ---- define('VIRTUAL_PATH', '/wiki'); ! Section 3 + To retain your PhpWiki logs between system restarts you should specify + a non-temporary directory. I recommend you use the same folder where + the web-server stores it's logs. Change the following (line 73) in + index.php from: + define('ACCESS_LOG', '/tmp/wiki_access_log'); *************** *** 226,230 **** Also by using this file, if you are updating or adding a tranlastion to the './phpwiki/locale/po/' files, you do not have to run 'make' ! from the terminal window. The Build target settings have been preconfigured to automatically build the project with a "legacy Makefile", by invoking '/usr/bin/gnumake' in the folder --- 233,237 ---- Also by using this file, if you are updating or adding a tranlastion to the './phpwiki/locale/po/' files, you do not have to run 'make' ! from the terminal window. The Build Target settings have been preconfigured to automatically build the project with a "legacy Makefile", by invoking '/usr/bin/gnumake' in the folder *************** *** 239,257 **** ----------------------------------- ! Project Builder 1.1.1 can be used with Sourceforge's CVS but there is ! a little bit of work to get it set up the first time. The following ! instructions were based on a tip from macosxhints.com. ! Preparation: ! Checkout phpwiki with the cvs command line tools. Make sure that your ! ssh keys have been uploaded to your account at Sourceforge and that ! you can sucessfully ssh into phpwiki.sourceforge.net. ! Instructions: ! 1. Download and install "keychain" from: ! <http://www.gentoo.org/projects/keychain.html>. The Keychain script acts as a front-end to ssh-agent, allowing you to --- 246,266 ---- ----------------------------------- ! Project Builder 1.1.1 (December 2001 Dev Tools) can be used with ! SourceForge's CVS but a little work is needed to get it set up the ! first time. The following instructions were based on a tip from ! macosxhints.com. ! Preparation ! Make sure that your ssh keys have been uploaded to your account at ! SourceForge and that you can sucessfully ssh into your account. Next, ! ensure that you can check out your project from SourceForge using the ! unix command-line based CVS tools provided by Mac OS X. ! Instructions ! 1. Download and install "keychain" from: ! <http://www.gentoo.org/projects/keychain.html> The Keychain script acts as a front-end to ssh-agent, allowing you to *************** *** 259,266 **** per login session. This dramatically reduces the number of times you need to enter your passphrase, from once per new terminal window ! session to once every time your local machine is rebooted. ! 2. Add the following to your .cshrc file (if you use the default tcsh ! shell or csh). setenv CVS_RSH 'ssh' --- 268,278 ---- per login session. This dramatically reduces the number of times you need to enter your passphrase, from once per new terminal window ! session to once every time your local machine is rebooted. It also ! allows you to use Project Builder with SSH instead of RSH. SSH is ! required if you want to commit files to a CVS repository at ! SourceForge. ! 2. If you use the default tcsh shell or csh, add the following to your ! .cshrc file: setenv CVS_RSH 'ssh' *************** *** 272,305 **** alias sshsf 'ssh mys...@ph...' ! (bash users would substitute the following lines in the above script ! for their .bashrc file:) CVS_RSH=ssh; EXPORT CVS_RSH source ~/.ssh-agent-${HOSTNAME} alias sshsf='ssh mys...@ph...' ! 3. Close the terminal window then open a new one. Keychain will ! activate ssh-agent which will ask for your ssh key password. It ! keeps running in the background and won't ask for your password ! again until you log out or restart. ! ! 4. From now on, YOU MUST open Project Builder from the Terminal shell ! for it's CVS to work with SSH. This is why We created a command ! alias in .cshrc to launch Project Builder. If it is already running ! because you double-clicked the PB icon, quit it, then launch it ! from the terminal by typing pb. Once PB is running you can safely ! double-click a project file to open it. Using the above method, ProjectBuilder will successfully connect to the Sourceforge CVS with SSH. Any other server which requires cvs ! connections via ssh instead of rsh should work too. ! Note: Renaming /usr/bin/rsh and replacing it with ssh doesn't seem to ! work; Project Builder simply MUST be launched from the command line ! for it to work at all with ssh. ! ! Hopefully SSH support will be improved in the future. Send an email ! to: mac...@gr... to let the team know that ! full support for SSH in Project Builder is important. --- 284,321 ---- alias sshsf 'ssh mys...@ph...' ! If you use bash instead, add following lines to the .bashrc file: CVS_RSH=ssh; EXPORT CVS_RSH + # Keychain is an OpenSSH key manager + # This will add my SSH1 and SSH2 key + /usr/bin/keychain ~/.ssh/id_rsa ~/.ssh/id_dsa source ~/.ssh-agent-${HOSTNAME} alias sshsf='ssh mys...@ph...' ! 3. Close the terminal window then open a new one. Keychain will ! activate ssh-agent which will ask for your ssh key password. It ! keeps running in the background and won't ask for your password ! again until you log out or restart. ! ! 4. From now on, YOU MUST open Project Builder from the Terminal shell ! for it's CVS to work with SSH. This is why we created a command ! alias in .cshrc to launch Project Builder. If it is already ! running because you double-clicked the PB icon, quit it, then ! launch it from the terminal by typing pb. <em>Once PB is running ! you can safely double-click a project file to open it</em>. Using the above method, ProjectBuilder will successfully connect to the Sourceforge CVS with SSH. Any other server which requires cvs ! connections to be made cia ssh instead of rsh should now work too. ! ! Note: Renaming /usr/bin/rsh to something else and replacing it with ! ssh doesn't seem to work; Project Builder simply MUST be ! launched from the command line for it to work at all with ssh. ! ! Hopefully Project Builder's integrated CVS will be improved in the ! future to directly support SSH. To let Apple know that full support ! for SSH in Project Builder is important, send an email to: ! <mac...@gr...> *************** *** 310,315 **** for some common Emacs stuff: *Note the wrapped url! ! http://developer.apple.com/techpubs/macosx/Cocoa/TasksAndConcepts/ ! ProgrammingTopics/TextDisplay/Tasks/TextDefaultsAndBindings.html --- 326,331 ---- for some common Emacs stuff: *Note the wrapped url! ! <http://developer.apple.com/techpubs/macosx/Cocoa/TasksAndConcepts/ ! ProgrammingTopics/TextDisplay/Tasks/TextDefaultsAndBindings.html> *************** *** 320,322 **** car...@ma... ! $Id$ --- 336,338 ---- car...@ma... ! $Id$ \ No newline at end of file |