什么是新的 Symfony 3 目录结构? [英] What is the new Symfony 3 directory structure?

查看：25 发布时间：2021/9/3 18:51:02 symfony

本文介绍了什么是新的 Symfony 3 目录结构?的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！

问题描述

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

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

终端问我:

<块引用>

您想使用 Symfony 3 目录结构吗?

这个 Symfony 3 目录结构是什么? 我以前从未见过...它是 2.5 之后的新版本吗?

使用它有什么好处?

有没有办法复制这个目录结构?

解决方案

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

问题 Would you like to use Symfony 3 directory structure? 在创建新项目时已被删除，因为它引起了混乱.您可以使用以下命令强制使用目录结构:

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

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

# .bash_profile# 所有新的 composer 安装都会询问`你想使用新的 Symfony3 结构吗?`导出 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，composer 将询问您是否要使用新的目录结构.

继续阅读下面的 Symfony2 和 Symfony3 目录结构之间的所有变化.

<小时>

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

(以及它如何影响我和我的工作流程)

我通过创建 2 个项目来研究这个问题，一个使用 symfony-2.5.0 目录结构，一个使用 symfony-3(仅更改目录结构).

为每个项目制作一个:

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

现在我们有了要比较的 2 个不同的目录.

<小时>

找到`diff`erence

您可以使用以下方法在两个目录之间diff:

$ diff -rq symfony-2.5.0/symfony-3//**(从差异返回)文件 symfony-2.5.0/.gitignore 和 symfony-3/.gitignore 不同文件 symfony-2.5.0/.travis.yml 和 symfony-3/.travis.yml 不同仅在 symfony-2.5.0/app: bootstrap.php.cache仅在 symfony-2.5.0/app: 缓存仅在 symfony-2.5.0/app: 控制台仅在 symfony-2.5.0/app: 日志仅在 symfony-2.5.0/app: phpunit.xml.dist仅在 symfony-3/bin: 控制台仅在 symfony-3/bin: symfony_requirements文件 symfony-2.5.0/composer.json 和 symfony-3/composer.json 不同仅在 symfony-3/: phpunit.xml.dist仅在 symfony-3/: var文件 symfony-2.5.0/vendor/autoload.php 和 symfony-3/vendor/autoload.php 不同文件 symfony-2.5.0/vendor/composer/autoload_real.php 和 symfony-3/vendor/composer/autoload_real.php 不同文件 symfony-2.5.0/web/app.php 和 symfony-3/web/app.php 不同文件 symfony-2.5.0/web/app_dev.php 和 symfony-3/web/app_dev.php 不同*/

这显示了两个版本中不同的文件.

<小时>

`diff`

的细分

这是差异中所有内容的细分.

#这些文件在两个版本中仍然存在(内容不同).gitignore.travis.yml作曲家.json供应商/自动加载.php供应商/作曲家/autoload_real.php网页/app.php网络/app_dev.php# 以下文件已从 2.5.0 中删除# {RemovedFile2.5} |{ReplacedWith3.0}应用程序/缓存|变量/缓存应用程序/日志|变量/日志应用程序/bootstrap.php.cache |var/bootstrap.php.cache应用程序/控制台 |垃圾箱/控制台app/phpunit.xml.dist |phpunit.xml.dist# 以下文件是 3.0 新增的bin/symfony_requirements # 通过 CLI 运行

<小时>

Symfony 3 目录结构的好处

新的目录结构有很多好处，所有这些都是次要的，可能只需要对您的工作流程进行最少的更改.

PHPUnit

phpunit 可以从项目根目录运行，无需明确指定配置文件的路径.

# Symfony2phpunit -c 应用程序/phpunit.xml# Symfony3(无需指定配置文件位置)phpunit

二进制可执行文件

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

# 你可以更新你的 `PATH` 以包含 `bin` 目录PATH="./bin:$PATH"# 从你的项目根目录，你现在可以像这样运行可执行文件:安慰symfony_requirements教义# 否则没有 `PATH` 更新垃圾箱/控制台bin/symfony_requirements垃圾箱/教义

新的`/var`目录

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

这也使得添加权限变得更加容易，整个 /var 目录应该可以被您的网络服务器写入.您可以按照
_{(来源:symfony.com)}

I just created a new Symfony 2.5 project with a regular composer command:

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

The Terminal asks me:

Would you like to use Symfony 3 directory structure?

What is this Symfony 3 directory structure? I have never seen it before... Is it new since 2.5?

What are the benefits to using it?

Is there any way to replicate this directory structure?

解决方案

I want to use the new Symfony 3 directory structure, but I don't see the question?

The question Would you like to use Symfony 3 directory structure? has been removed when creating a new project due to the confusion it caused. You can force the use of the directory structure using the following:

If you prefer the new structure, you can add the environment variable SENSIOLABS_ENABLE_NEW_DIRECTORY_STRUCTURE to your .bashrc or .bash_profile like so:

Make all future projects ask for the new structure

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

Make ONLY THIS project ask if we want to use the new structure.

If you wanted it for a particular project only (a one off), you can use:

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

If the environment variable SENSIOLABS_ENABLE_NEW_DIRECTORY_STRUCTURE is set and set to true, composer will ask if you want to use the new directory structure.

Continue reading below for all the changes between the Symfony2 and Symfony3 directory structure.

What is the new Symfony 3 directory structure?

(and how does it effect me & my workflow)

I looked into this by creating 2 projects, one with symfony-2.5.0 directory structure, one with symfony-3 (directory structure change only).

Make one of each project:

# 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

So now we have the 2 different directories we want to compare.

Find the `diff`erence

You can diff between the 2 directories using:

$ 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
*/

This shows the files that differ in the 2 versions.

Breakdown of `diff`

Here's a breakdown of everything in the diff.

# 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

Benefits of the Symfony 3 directory structure

The new directory structure has a number of benefits, all of which are minor and may require minimal changes to your workflow.

PHPUnit

phpunit can be run from the project root without having to explicitly specify the path of the configuration file.

# Symfony2
phpunit -c app/phpunit.xml

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

Binary Executables

All binary executable files are now all located in a single location - the bin directory (similar to a unix-like os).

# 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

The new `/var` directory

The new /var directory contains the files to which the system writes data to during the course of its operation (similar to a unix-like os).

This also makes it easier to add permissions, the entire /var directory should be writable by your webserver. You can follow the Symfony2 guide for setting permissions (substituting app/cache && app/logs with var), any other files you want to write locally could also be located here.

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

Symfony requirements check

Running symfony_requirements will output mandatory & optional environment configurations.
e.g:

********************************
* '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)
'

Conclusion

Looks like a good tidy up by Sensio Labs, all the above changes make perfect sense, they should be easy to implement when upgrading from 2.5 to 3.x, these will probably be the least of your problems!

Read the docs

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

Release Date for Symfony 3

It looks far off looking at the Release process (worth a read):

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

_{(source: symfony.com)}

这篇关于什么是新的 Symfony 3 目录结构?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！

查看全文

什么是新的 Symfony 3 目录结构? [英] What is the new Symfony 3 directory structure?

问题描述

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

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

只让这个项目询问我们是否要使用新结构.

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

找到`diff`erence

`diff`

Symfony 3 目录结构的好处

PHPUnit

二进制可执行文件

新的`/var`目录

I want to use the new Symfony 3 directory structure, but I don't see the question?

Make all future projects ask for the new structure

Make ONLY THIS project ask if we want to use the new structure.

What is the new Symfony 3 directory structure?

Find the `diff`erence

Breakdown of `diff`

Benefits of the Symfony 3 directory structure

PHPUnit

Binary Executables

The new `/var` directory

Symfony requirements check

Conclusion

Read the docs

Release Date for Symfony 3

相关文章

其他开发最新文章

热门教程

热门工具

登录关闭

什么是新的 Symfony 3 目录结构? [英] What is the new Symfony 3 directory structure?

问题描述

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

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

只让这个项目询问我们是否要使用新结构.

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

找到difference

diff

Symfony 3 目录结构的好处

PHPUnit

二进制可执行文件

新的/var目录

I want to use the new Symfony 3 directory structure, but I don't see the question?

Make all future projects ask for the new structure

Make ONLY THIS project ask if we want to use the new structure.

What is the new Symfony 3 directory structure?

Find the difference

Breakdown of diff

Benefits of the Symfony 3 directory structure

PHPUnit

Binary Executables

The new /var directory

Symfony requirements check

Conclusion

Read the docs

Release Date for Symfony 3

相关文章

其他开发最新文章

热门教程

热门工具

登录 关闭

找到`diff`erence

`diff`

新的`/var`目录

Find the `diff`erence

Breakdown of `diff`

The new `/var` directory

登录关闭