array ( 0 => 'index.php', 1 => 'PHP Manual', ), 'head' => array ( 0 => 'UTF-8', 1 => 'tr', ), 'this' => array ( 0 => 'phar.creating.intro.php', 1 => 'Creating Phar Archives: Introduction', 2 => 'Creating Phar Archives: Introduction', ), 'up' => array ( 0 => 'phar.creating.php', 1 => 'Creating Phar Archives', ), 'prev' => array ( 0 => 'phar.creating.php', 1 => 'Creating Phar Archives', ), 'next' => array ( 0 => 'phar.fileformat.php', 1 => 'What makes a phar a phar and not a tar or a zip?', ), 'alternatives' => array ( ), 'source' => array ( 'lang' => 'en', 'path' => 'reference/phar/creating.xml', ), 'history' => array ( ), ); $setup["toc"] = $TOC; $setup["toc_deprecated"] = $TOC_DEPRECATED; $setup["parents"] = $PARENTS; manual_setup($setup); contributors($setup); ?>

Creating Phar Archives: Introduction

To be written fully in the near future. Before reading this, be sure to read How to use Phar Archives.

A great place to start is by reading about Phar::buildFromIterator(), and the specifics of the file format choices available for archives. A healthy understanding of what a stub is and does is crucial to phar archive creation, and so Phar::setStub() and Phar::createDefaultStub() are good places to start as well. If you are distributing a web-based application, it is crucial to know about Phar::webPhar() and related method Phar::mungServer(). Any application that accesses its own files should also consider using Phar::interceptFileFuncs().