- Timestamp:
- 04/19/06 17:09:31 (3 years ago)
- Files:
-
- trunk/doc/book/content/project_creation.txt (modified) (5 diffs)
- trunk/doc/book/content/upload.txt (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
trunk/doc/book/content/project_creation.txt
r1067 r1233 64 64 web/ 65 65 66 The `symfony` command should always be called from this directory to apply to the current project. 66 >**Note**: If you have specific requirements for your project, symfony can adapt to any custom file structure. All the paths in the symfony scripts use a set of special parameters defined in a file called `constants.php`, which can be customized as described in the [file structure chapter](file_structure.txt). 67 68 The `symfony` command must always be called from a project root directory (`myproject/` in the example above), because all the tasks perfomed by this command are project specific. If called from one of the project subdirectories, the command will raise an error. 67 69 68 70 Application Setup … … 91 93 `index.php` is the *production* front controller of the new application. Because you created the first application of the project, Symfony created a file called `index.php` instead of `myapp.php` (if you now add a new application called `mynewapp`, the new production front controller will be named `mynewapp.php`). To run your application in the *development* environment, call the front controller `myapp_dev.php`. 92 94 93 >**Note**: if you carefully read the introduction, you may wonder where the `myapp_test.php` file is located. As a matter of fact, the *test* environment is used to do unit testing of your applications components and doesn't require a front controller. Refer to the [unit testing chapter](test_unit_testing.txt) to learn more about it.95 >**Note**: If you carefully read the introduction, you may wonder where the `myapp_test.php` file is located. As a matter of fact, the *test* environment is used to do unit testing of your applications components and doesn't require a front controller. Refer to the [unit testing chapter](test_unit_testing.txt) to learn more about it. 94 96 95 97 From now on, the `/home/steve/myproject/` directory will be considered as the root of your project. The root path is stored in a constant called `SF_ROOT_DIR`, defined in the file `index.php`, and we will use this name instead of the real path to avoid confusing the readers who aren't named Steve. … … 101 103 102 104 <Directory "/$data_dir/symfony/web/sf"> 103 AllowOverride All104 Allow from All105 AllowOverride All 106 Allow from All 105 107 </Directory> 106 108 <VirtualHost *:80> … … 111 113 112 114 <Directory "/home/steve/myproject/web"> 113 AllowOverride All114 Allow from All115 AllowOverride All 116 Allow from All 115 117 </Directory> 116 118 </VirtualHost> … … 173 175 The example below assumes that $SVNREP_DIR is defined as an environment variable. If you don't have it defined, you will need to substitute the actual location of the repository in place of $SVNREP_DIR. 174 176 175 So let s **create** the new repository for the `myproject` project:177 So let's **create** the new repository for the `myproject` project: 176 178 177 179 $ svnadmin create $SVNREP_DIR/myproject trunk/doc/book/content/upload.txt
r1231 r1233 10 10 ------------------- 11 11 12 Uploading a file requires a form in a template, and an action to handle it. For the template, use the ` file_upload_tag()` helper in a form declared as `multipart`:12 Uploading a file requires a form in a template, and an action to handle it. For the template, use the `input_file_tag()` helper in a form declared as `multipart`: 13 13 14 14 [php]
