symfony2 – 什么是新的Symfony 3目录结构?

我刚刚创建了一个新的Symfony 2.5项目与常规composer命令:

php composer.phar create-project symfony/framework-standard-edition path/ 2.5.0

终端问我:

Would you like to use Symfony 3 directory structure?

这个Symfony 3的目录结构是什么?我从来没有见过它…从2.5是新的吗?

使用它有什么好处?

有什么办法复制这个目录结构吗?

我想使用新的Symfony 3目录结构,但我没有看到问题?

问题你想使用Symfony 3的目录结构吗?已经删除,当创建一个新的项目,由于它造成的混乱。您可以使用以下命令强制使用目录结构:

如果您喜欢新结构,可以将环境变量SENSIOLABS_ENABLE_NEW_DIRECTORY_STRUCTURE添加到.bashrc或.bash_profile中,如下所示:

让所有未来的项目都要求新的结构

# .bash_profile
# ALL new composer installs will ask `Would you like to use the new Symfony3 strucure?`
export SENSIOLABS_ENABLE_NEW_DIRECTORY_STRUCTURE=true

只有这个项目询问我们是否要使用新的结构。

如果你只想要一个特定的项目(一次性),你可以使用:

SENSIOLABS_ENABLE_NEW_DIRECTORY_STRUCTURE=true composer create-project symfony/framework-standard-edition path/ "2.5.*"

如果环境变量SENSIOLABS_ENABLE_NEW_DIRECTORY_STRUCTURE设置为true,组合器将询问您是否要使用新的目录结构。

继续阅读以下Symfony2和Symfony3目录结构之间的所有更改。

什么是新的Symfony 3目录结构?

(它如何影响我&我的工作流程)

我通过创建2个项目,一个与symfony-2.5.0目录结构,一个与symfony-3(目录结构更改只有)研究这个。

制作每个项目之一:

# say `N` to `Would you like to use Symfony 3 directory structure?`
$ composer create-project symfony/framework-standard-edition symfony-2.5.0/ 2.5.0

# say `Y` to `Would you like to use Symfony 3 directory structure?`
$ composer create-project symfony/framework-standard-edition symfony-3/ 2.5.0

所以现在我们有两个不同的目录,我们想比较。

找到区别

你可以在两个目录之间使用:

$ diff -rq symfony-2.5.0/ symfony-3/
/** (Returned from the diff)
Files symfony-2.5.0/.gitignore and symfony-3/.gitignore differ
Files symfony-2.5.0/.travis.yml and symfony-3/.travis.yml differ
Only in symfony-2.5.0/app: bootstrap.php.cache
Only in symfony-2.5.0/app: cache
Only in symfony-2.5.0/app: console
Only in symfony-2.5.0/app: logs
Only in symfony-2.5.0/app: phpunit.xml.dist
Only in symfony-3/bin: console
Only in symfony-3/bin: symfony_requirements
Files symfony-2.5.0/composer.json and symfony-3/composer.json differ
Only in symfony-3/: phpunit.xml.dist
Only in symfony-3/: var
Files symfony-2.5.0/vendor/autoload.php and symfony-3/vendor/autoload.php differ
Files symfony-2.5.0/vendor/composer/autoload_real.php and symfony-3/vendor/composer/autoload_real.php differ
Files symfony-2.5.0/web/app.php and symfony-3/web/app.php differ
Files symfony-2.5.0/web/app_dev.php and symfony-3/web/app_dev.php differ
*/

这显示在2个版本中不同的文件。

差异的分解

这里是差异的一切细目。

# These files still exist in both versions (with different content)
.gitignore
.travis.yml
composer.json
vendor/autoload.php
vendor/composer/autoload_real.php
web/app.php
web/app_dev.php

# The following files have been removed from 2.5.0
# {RemovedFile2.5}      |  {ReplacedWith3.0}
app/cache               |  var/cache
app/logs                |  var/log
app/bootstrap.php.cache |  var/bootstrap.php.cache
app/console             |  bin/console
app/phpunit.xml.dist    |  phpunit.xml.dist

# The following files are new in 3.0
bin/symfony_requirements # run via CLI

Symfony 3目录结构的优点

新的目录结构具有许多优点,所有这些都是次要的,并且可能需要对工作流程进行最少的更改。

PHPUnit

phpunit可以从项目根运行,而不必显式指定配置文件的路径。

# Symfony2
phpunit -c app/phpunit.xml

# Symfony3 (no need to specify the configuration file location)
phpunit

二进制可执行文件

所有二进制可执行文件现在都位于单个位置 – bin目录(类似于类Unix的操作系统)。

# you can update your `PATH` to include the `bin` directory
PATH="./bin:$PATH"

# From your project root you can now run executables like so:
console
symfony_requirements
doctrine

# else with no `PATH` update
bin/console
bin/symfony_requirements
bin/doctrine

新的/ var目录

新的/ var目录包含系统在其操作过程中向其写入数据的文件(类似于类Unix的操作系统)。

这也使得更容易添加权限,整个/ var目录应该是可写的您的web服务器。你可以按照Symfony2 guide for setting permissions(用var替换app / cache&& app / logs),你想在本地写的任何其他文件也可以放在这里。

# default symfony3 `var` directory
var/bootstrap.php.cache
var/cache
var/logs

Symfony需求检查

运行symfony_requirements将输出强制&可选环境配置。
例如:

********************************
* 'Symfony requirements check' *
********************************

* Configuration file used by PHP: /usr/local/php5/lib/php.ini

/** ATTENTION **
*  The PHP CLI can use a different php.ini file
*  than the one used with your web server.
*  To be on the safe side, please also launch the requirements check
*  from your web server using the web/config.php script.
*/

** Mandatory requirements **
'
 OK       PHP version must be at least 5.3.3 (5.5.11 installed)
 OK       PHP version must not be 5.3.16 as Symfony wont work properly with it
 OK       Vendor libraries must be installed
 OK       var/cache/ directory must be writable
 OK       var/logs/ directory must be writable
 OK       date.timezone setting must be set
 OK       Configured default timezone "Europe/London" must be supported by your installation of PHP
 OK       json_encode() must be available
 OK       session_start() must be available
 OK       ctype_alpha() must be available
 OK       token_get_all() must be available
 OK       simplexml_import_dom() must be available
 OK       APC version must be at least 3.1.13 when using PHP 5.4
 OK       detect_unicode must be disabled in php.ini
 OK       xdebug.show_exception_trace must be disabled in php.ini
 OK       xdebug.scream must be disabled in php.ini
 OK       PCRE extension must be available
'
** Optional recommendations **
'
 OK       xdebug.max_nesting_level should be above 100 in php.ini
 OK       Requirements file should be up-to-date
 OK       You should use at least PHP 5.3.4 due to PHP bug #52083 in earlier versions
 OK       When using annotations you should have at least PHP 5.3.8 due to PHP bug #55156
 OK       You should not use PHP 5.4.0 due to the PHP bug #61453
 OK       When using the logout handler from the Symfony Security Component, you should have at least PHP 5.4.11 due to PHP bug #63379 (as a workaround, you can also set invalidate_session to false in the security logout handler configuration)
 OK       You should use PHP 5.3.18+ or PHP 5.4.8+ to always get nice error messages for fatal errors in the development environment due to PHP bug #61767/#60909
 OK       PCRE extension should be at least version 8.0 (8.34 installed)
 OK       PHP-XML module should be installed
 OK       mb_strlen() should be available
 OK       iconv() should be available
 OK       utf8_decode() should be available
 OK       posix_isatty() should be available
 OK       intl extension should be available
 OK       intl extension should be correctly configured
 OK       intl ICU version should be at least 4+
 OK       a PHP accelerator should be installed
 OK       short_open_tag should be disabled in php.ini
 OK       magic_quotes_gpc should be disabled in php.ini
 OK       register_globals should be disabled in php.ini
 OK       session.auto_start should be disabled in php.ini
 OK       PDO should be installed
 OK       PDO should have some drivers installed (currently available: mysql, sqlite, dblib, pgsql)
'

结论

看起来像一个很好的整理由Sensio实验室,所有上述变化都是完美的,他们应该很容易实现,当从2.5升级到3.x,这些可能是你的问题的最少!

阅读文档

Symfony 2.x => 3.0 Upgrade docs here
Symfony 3.0 The Architecture

Symfony 3的发行日期

它看起来很远,看看发布过程(值得一读):

http://symfony.com/doc/current/contributing/community/releases.html

http://stackoverflow.com/questions/23993295/what-is-the-new-symfony-3-directory-structure

本站文章除注明转载外,均为本站原创或编译
转载请明显位置注明出处:symfony2 – 什么是新的Symfony 3目录结构?