Changeset 19971
- Timestamp:
- 07/07/09 11:16:15 (7 months ago)
- Files:
-
- doc/branches/1.0/book/03-Running-Symfony.txt (modified) (1 diff)
- doc/branches/1.1/book/03-Running-Symfony.txt (modified) (1 diff)
- doc/branches/1.2/book/03-Running-Symfony.txt (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
doc/branches/1.0/book/03-Running-Symfony.txt
r19818 r19971 240 240 </VirtualHost> 241 241 242 In the configuration in Listing 3-1, the `$sf_symfony_data_dir` placeholder must be replaced by the actual path. For example, for a PEAR installation in *nix, you should type something like this: 242 In the configuration in Listing 3-1, the `$sf_symfony_data_dir` placeholder 243 must be replaced by the actual path. For example, for a PEAR installation in 244 *nix, you should type something like this: 243 245 244 246 Alias /sf /usr/local/lib/php/data/symfony/web/sf 245 247 246 248 >**NOTE** 247 >The alias to the `web/sf/` directory is not mandatory. It allows Apache to find images, style sheets, and JavaScript files for the web debug toolbar, the admin generator, the default symfony pages, and the Ajax support. An alternative to this alias would be to create a symbolic link (symlink) or copy the `/path/to/symfony/data/web/sf/` directory to `myproject/web/sf/`. 248 249 Restart Apache, and that's it. Your newly created application can now be called and viewed through a standard web browser at the following URL: 249 >The alias to the `web/sf/` directory is not mandatory. It allows Apache to 250 find images, style sheets, and JavaScript files for the web debug toolbar, 251 the admin generator, the default symfony pages, and the Ajax support. 252 An alternative to this alias would be to create a symbolic link (symlink) or 253 copy the `/path/to/symfony/data/web/sf/` directory to `myproject/web/sf/`. 254 255 >**TIP** 256 >If you have installed symfony via PEAR and can't find the symfony shared data 257 >directory, look in the PEAR `data_dir` which is listed in the PEAR config: 258 > 259 > pear config-show 260 261 Restart Apache, and that's it. Your newly created application can now be called 262 and viewed through a standard web browser at the following URL: 250 263 251 264 http://localhost/myapp_dev.php/ doc/branches/1.1/book/03-Running-Symfony.txt
r19818 r19971 241 241 </VirtualHost> 242 242 243 In the configuration in Listing 3-1, the `$sf_symfony_data_dir` placeholder must be replaced by the actual path. For example, for a PEAR installation in *nix, you should type something like this: 244 245 Alias /sf /usr/local/lib/php/data/symfony/web/sf 243 In the configuration in Listing 3-1, the `$sf_symfony_data_dir` placeholder 244 must be replaced by the actual path. For example, for a PEAR installation in 245 *nix, you should type something like this: 246 247 Alias /sf /usr/local/lib/php/data/symfony/web/sf 246 248 247 249 >**NOTE** 248 >The alias to the `web/sf/` directory is not mandatory. It allows Apache to find images, style sheets, and JavaScript files for the web debug toolbar, the admin generator, the default symfony pages, and the Ajax support. An alternative to this alias would be to create a symbolic link (symlink) or copy the `/path/to/symfony/data/web/sf/` directory to `myproject/web/sf/`. 249 250 Restart Apache, and that's it. Your newly created application can now be called and viewed through a standard web browser at the following URL: 250 >The alias to the `web/sf/` directory is not mandatory. It allows Apache to 251 find images, style sheets, and JavaScript files for the web debug toolbar, 252 the admin generator, the default symfony pages, and the Ajax support. 253 An alternative to this alias would be to create a symbolic link (symlink) or 254 copy the `/path/to/symfony/data/web/sf/` directory to `myproject/web/sf/`. 255 256 >**TIP** 257 >If you have installed symfony via PEAR and can't find the symfony shared data 258 >directory, look in the PEAR `data_dir` which is listed in the PEAR config: 259 > 260 > pear config-show 261 262 Restart Apache, and that's it. Your newly created application can now be called 263 and viewed through a standard web browser at the following URL: 251 264 252 265 http://localhost/frontend_dev.php/ doc/branches/1.2/book/03-Running-Symfony.txt
r19818 r19971 240 240 </VirtualHost> 241 241 242 In the configuration in Listing 3-1, the `$sf_symfony_data_dir` placeholder must be replaced by the actual path. For example, for a PEAR installation in *nix, you should type something like this: 243 244 Alias /sf /usr/local/lib/php/data/symfony/web/sf 242 In the configuration in Listing 3-1, the `$sf_symfony_data_dir` placeholder 243 must be replaced by the actual path. For example, for a PEAR installation in 244 *nix, you should type something like this: 245 246 Alias /sf /usr/local/lib/php/data/symfony/web/sf 245 247 246 248 >**NOTE** 247 >The alias to the `web/sf/` directory is not mandatory. It allows Apache to find images, style sheets, and JavaScript files for the web debug toolbar, the admin generator, the default symfony pages, and the Ajax support. An alternative to this alias would be to create a symbolic link (symlink) or copy the `/path/to/symfony/data/web/sf/` directory to `myproject/web/sf/`. 248 249 Restart Apache, and that's it. Your newly created application can now be called and viewed through a standard web browser at the following URL: 249 >The alias to the `web/sf/` directory is not mandatory. It allows Apache to 250 find images, style sheets, and JavaScript files for the web debug toolbar, 251 the admin generator, the default symfony pages, and the Ajax support. 252 An alternative to this alias would be to create a symbolic link (symlink) or 253 copy the `/path/to/symfony/data/web/sf/` directory to `myproject/web/sf/`. 254 255 >**TIP** 256 >If you have installed symfony via PEAR and can't find the symfony shared data 257 >directory, look in the PEAR `data_dir` which is listed in the PEAR config: 258 > 259 > pear config-show 260 261 Restart Apache, and that's it. Your newly created application can now be called 262 and viewed through a standard web browser at the following URL: 250 263 251 264 http://localhost/frontend_dev.php/

