phpgtk__legacy/wiki/wikilib.d/PmWiki.Installation

version=pmwiki-2.1.11 ordered=1 urlencoded=1
agent=Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
author=
csum=
host=70.49.175.50
name=PmWiki.Installation
passwdedit=id:anshu
rev=213
targets=PmWiki.Requirements,PmWiki.Upgrades,PmWiki.WikiFarms,PmWiki.ChangeLog,PmWiki.MailingLists,PmWiki.InitialSetupTasks,PmWiki.ReleaseNotes,PmWiki.Internationalizations,PmWiki.SimultaneousEdits,PmWiki.Troubleshooting,PmWiki.DocumentationIndex
text=(:title PmWiki Installation :)%0a%25audience%25 administrators (basic)%0aThis page explains how to download and install PmWiki 2.1.  Here's a list of related pages:%0a%0a* [[Requirements]] - Requirements for installing PmWiki.%0a* [[Upgrades]] - How to upgrade an existing installation.%0a* [[WikiFarms]] - Running multiple wikis from a single installation.%0a* [[ChangeLog]] -  New features and bug fixes that are available.%0a%0aImprovements to these instructions are always appreciated.  Just report any problems you  encounter to the pmwiki-users [[mailing list(s)]] or use the [[PITS:PITS |PmWiki Issue Tracking System]].%0a%0a!! Installing PmWiki%0a%0a!!! 1. Download%0aDownload the latest version of PmWiki as a zip archive ([[(http://www.pmwiki.org/pub/pmwiki/)pmwiki-latest.zip]]) or a gzipped tarball ([[(http://www.pmwiki.org/pub/pmwiki/)pmwiki-latest.tgz]]) from [[http://www.pmwiki.org/pub/pmwiki/]].%0a%0a%0a!!! [[#unpack]] 2. Unpack%0aUnpack the archive ([@tar zxvf pmwiki-latest.tgz@] or [@unzip pmwiki-latest.zip@]).  This will create a ''pmwiki-x.y.z'' directory containing the PmWiki software.  For example, the current "latest" should unpack to a directory named ''{$Version}''.  The files in this directory include:%0a%0a    README.txt        An introductory document%0a    pmwiki.php        The main PmWiki script%0a    local/            Configuration scripts (local configuration files)%0a    cookbook/         Recipes (add-ons) from the [[(Cookbook:)Cookbook]]%0a    docs/             Brief documentation, sample configuration scripts%0a    pub/              Publicly accessible files%0a      css/            Extra CSS stylesheet files%0a      skins/          Layout templates for [[Cookbook:Skins|custom]] look and feel%0a    scripts/          Scripts that are part of PmWiki%0a    wikilib.d/        Bundled default PmWiki pages%0a%0aThe ''pmwiki-x.y.z'' directory needs to be placed into a location accessible by your webserver (e.g., in a ''public_html'' directory of some sort).  You can place files and directories using a number of methods -- FTP, or a Unix [@mv@] or [@cp@] command generally does the job.%0a%0a->%25note%25 Note: It's probably also a good idea to change the "''pmwiki-x.y.z''" directory name to be simply "''pmwiki''".%0a%0a%0a!!! [[#directories]] 3. Create directories%0a[[#dirsetup]]In most cases PmWiki will do this for you.%0aOpen a web browser to the ''pmwiki.php'' script on the server (i.e., not the one on your local computer or accessed using a [=file://...=] URL).  PmWiki will then analyze your system configuration and provide instructions (if needed) for creating the ''wiki.d/'' directory which will be used to hold the pages created for your site.  %0a%0aOtherwise, there are two ways to achieve this.%0a%0a->3a. You can create the ''wiki.d/'' directory manually, and then give it full write permissions (i.e., "[@chmod 777 wiki.d@]"). Use this method when "safe mode" is activated in the servers PHP installation.%0a%0a->3b. On some systems you can let PmWiki create ''wiki.d/'' by temporarily changing the permissions on the directory containing the ''pmwiki.php'' file to 2777.  In Unix this is commonly done by changing to the directory containing ''pmwiki.php'' and executing the command%0a%0a        chmod 2777 .%0a%0a->(note the dot at the end). The [@chmod@] command also works in many FTP programs. Creating ''wiki.d/'' in this manner will (1) make the directory writable so the web server can create the data directory it needs for the wiki files, (2) preserve group ownership of the directory so the installer account can manipulate the files created in this directory, and (3) make it more difficult for other accounts on the same server to access the files in ''wiki.d/''.%0a%0aAfter establishing directory permissions, try opening a browser to the ''pmwiki.php'' script again.  If all is well, the ''wiki.d'' directory will have been created and you'll see the default home page.%0a%0aImportant: If you used method 3b, you should reset permissions by executing "[@chmod 755 .@]" in the directory containing pmwiki.php.%0a%0a[[#dirsetupend]]%0a!!! 4. Initialize%0aCheck out [[Initial Setup Tasks]] for other tasks you may want to perform to begin customizing your PmWiki installation.  You might also want to peruse the [[Release Notes]] for further information.%0a%0a%0a!!! 5. Set language%0aIf you want to use PmWiki in a different language download the international language pack as zip archive ([[(http://www.pmwiki.org/pub/pmwiki/)i18n.zip]]) or as gzipped tarball ([[(http://www.pmwiki.org/pub/pmwiki/)i18n.tgz]]) from [[http://www.pmwiki.org/pub/pmwiki/]]. Then extract it and copy the files into the ''wikilib.d/'' directory as described above.%0a%0aThere are two directories in the decompressed i18n archive, ''scripts'' and ''wikilib.d''. Copy the files respectively contained in these directories to the ''scripts'' and ''wikilib.d'' of your PmWiki directory. For example, for French localization,  PmWikiFr.* and PmWiki.* must be contained in the '''same''' directory.%0a%0aThen, enable localization by adding an instruction to local/config.php to load the language translation page of your choice. For instance,  [@XLPage('fr','PmWikiFr.XLPage');@] loads the French language page PmWikiFr.XLPage.%0a%0aRead more about this on [[Internationalizations]].%0a%0a!! [[#notes]] Notes%0a%0a* The PmWiki distribution deliberately doesn't include an ''index.php'' file.  Resist the temptation to rename ''pmwiki.php'' to ''index.php'' because if you rename the file it will not be overwritten during an upgrade.  Instead, add an ''index.php'' "wrapper script" with the following single line (missing a closing "[@ ?>@]" tag deliberately):%0a%0a-->[@%3c?php include('pmwiki.php');@]%0a%0a* If using the Unix ''tar'' command to unpack the archive in step 2 above, be sure that the files are created with sufficient permissions for the webserver to be able to access them.  Usually you can ensure this by typing @@umask 002@@ on the command line before unpacking the tar file.%0a%0a* When installing on Windows you should take a look at [[Cookbook:SimultaneousEdits]] to enable [[simultaneous edits]] on that platform.%0a%0a* Additional tips can be found at [[Troubleshooting]].%0a%0a%25trail%25%3c%3c|[[Documentation Index]]|>>%0a%0a%0a>>faq%3c%3c [[#faq]]%0a%0aQ: How do I make pmwiki.php the default page for a website?  Should I rename pmwiki.php to index.php?%0a%0aA: Renaming pmwiki.php is not recommended. Instead, create an ''index.php'' file that contains the single line:%0a%0a->[@%3c?php include_once('pmwiki.php');@]%0a%0aYou may also want to check [[Cookbook:CleanUrls]].%0a%0a%0aQ: Why does pmwiki.org appear to have a directory structure rather than "?n=pagename" in urls?%0a%0aA: Pmwiki.org uses a variant of [[Cookbook:CleanUrls]].%0a%0a%0aQ: Is it possible to move wiki.d to /tmp/persistent/wiki.d (a new sourceforge rule)?%0a%0aA: Sourceforge suggests moving everything to /tmp/persistent/new-folder-of-your-choice and creating a symbolic link to the new folder on /tmp . It works -- see [[Cookbook:SourceForgeServers]].%0a%0a%0aQ: How can I run PmWiki on a standalone (offline, portable) machine ?%0a%0aA: See [[Cookbook:Standalone]].
time=1152032843
title=PmWiki Installation