1 <?xml version="1.0" encoding="UTF-8"?>
3 <chapter id="introduction.installation">
4 <title>Installation</title>
7 See the <link linkend="requirements">requirements appendix</link> for a detailed list of
8 requirements for Zend Framework.
12 Installing Zend Framework is extremely simple. Once you have downloaded and extracted the
13 framework, you should add the <filename>/library</filename> folder in the distribution to
14 the beginning of your include path. You may also want to move the library folder
15 to another – possibly shared – location on your file system.
21 <ulink url="http://framework.zend.com/download/latest">Download the latest
22 stable release.</ulink> This version, available in both
23 <filename>.zip</filename> and <filename>.tar.gz</filename> formats, is a
24 good choice for those who are new to Zend Framework.
30 <ulink url="http://framework.zend.com/download/snapshot">Download the latest
31 nightly snapshot.</ulink> For those who would brave the cutting edge, the
32 nightly snapshots represent the latest progress of Zend Framework development.
33 Snapshots are bundled with documentation either in English only or in all
34 available languages. If you anticipate working with the latest Zend Framework
35 developments, consider using a Subversion (<acronym>SVN</acronym>) client.
41 Using a <ulink url="http://subversion.tigris.org">Subversion</ulink>
42 (<acronym>SVN</acronym>) client. Zend Framework is open source software, and the
43 Subversion repository used for its development is publicly available. Consider
44 using <acronym>SVN</acronym> to get Zend Framework if you already use
45 <acronym>SVN</acronym> for your application development, want to
46 contribute back to the framework, or need to upgrade your framework version
47 more often than releases occur.
51 <ulink url="http://svnbook.red-bean.com/nightly/en/svn.ref.svn.c.export.html">
52 Exporting</ulink> is useful if you want to get a particular framework revision
53 without the <filename>.svn</filename> directories as created in a working copy.
57 <ulink url="http://svnbook.red-bean.com/nightly/en/svn.ref.svn.c.checkout.html">
58 Check out a working copy</ulink> if you want contribute to Zend Framework, a
59 working copy can be updated any time with
60 <ulink url="http://svnbook.red-bean.com/nightly/en/svn.ref.svn.c.update.html">
61 svn update</ulink> and changes can be commited to our <acronym>SVN</acronym>
63 <ulink url="http://svnbook.red-bean.com/nightly/en/svn.ref.svn.c.commit.html">
64 svn commit</ulink> command.
69 <ulink url="http://svnbook.red-bean.com/nightly/en/svn.advanced.externals.html">
70 externals definition</ulink> is quite convenient for developers already using
71 <acronym>SVN</acronym> to manage their application's working copies.
75 The <acronym>URL</acronym> for the trunk of Zend Framework's <acronym>SVN</acronym>
77 url="http://framework.zend.com/svn/framework/standard/trunk">
78 http://framework.zend.com/svn/framework/standard/trunk</ulink>
84 Once you have a copy of Zend Framework available, your application needs to be able to
85 access the framework classes. Though there are
86 <ulink url="http://www.php.net/manual/en/configuration.changes.php">
87 several ways to achieve this</ulink>, your <acronym>PHP</acronym>
88 <ulink url="http://www.php.net/manual/en/ini.core.php#ini.include-path">include_path</ulink>
89 needs to contain the path to Zend Framework's library.
93 Zend provides a <ulink url="http://framework.zend.com/docs/quickstart">QuickStart</ulink>
94 to get you up and running as quickly as possible. This is an excellent way to begin
95 learning about the framework with an emphasis on real world examples that you can build
100 Since Zend Framework components are loosely coupled, you may use a somewhat unique
101 combination of them in your own applications. The following chapters provide a
102 comprehensive reference to Zend Framework on a component-by-component basis.