Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commitbbbfb10

Browse files
committed
Merge remote-tracking branch 'origin/master'
* origin/master: (38 commits) typo Clarifying that our code is just additions [#8732] Minor tweaks minor tweaks updating link to be version independent Adding yarn install text Reduce ambiguity of encore installation Remove svn & changelog articles Add instructions to install dependencies before using them Fixed some typos Fix upgrading to Flex Removed links to specific files (they are not easy to maintain) Correction in the console command folder Fixed some typos Updated the configuration/* files Add example usage of the link script Change service override docs removing need for annotation route import change linking directly and marking articles as orphans adding other dirs ...
2 parents2dd2a9f +991835d commitbbbfb10

File tree

43 files changed

+563
-5036
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

43 files changed

+563
-5036
lines changed

‎_build/redirection_map‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -283,7 +283,8 @@
283283
/cookbook/workflow/homestead /setup/homestead
284284
/cookbook/workflow/index /setup
285285
/cookbook/workflow/new_project_git /setup/new_project_git
286-
/cookbook/workflow/new_project_svn /setup/new_project_svn
286+
/cookbook/workflow/new_project_svn /setup/new_project_git
287+
/setup/new_project_svn /setup/new_project_git
287288
/components/asset/index /components/asset
288289
/components/asset/introduction /components/asset
289290
/components/browser_kit/index /components/browser_kit

‎best_practices/configuration.rst‎

Lines changed: 36 additions & 73 deletions
Original file line numberDiff line numberDiff line change
@@ -11,33 +11,33 @@ three parts.
1111
Infrastructure-Related Configuration
1212
------------------------------------
1313

14+
These are the options that change from one machine to another (e.g. from your
15+
development machine to the production server) but which don't change the
16+
application behavior.
17+
1418
..best-practice::
1519

16-
Define the infrastructure-related configuration options in the
17-
``app/config/parameters.yml`` file.
20+
Define the infrastructure-related configuration options as environment
21+
variables. During development, use the ``.env`` file at the root of your
22+
project to set these.
1823

19-
The default ``parameters.yml`` file follows this recommendation and defines the
20-
options related tothedatabase and mail server infrastructure:
24+
By default, Symfony adds these types of options to the ``.env`` file when
25+
installing new dependencies intheapp:
2126

22-
..code-block::yaml
27+
..code-block::bash
2328
24-
# app/config/parameters.yml
25-
parameters:
26-
database_driver:pdo_mysql
27-
database_host:127.0.0.1
28-
database_port:~
29-
database_name:symfony
30-
database_user:root
31-
database_password:~
29+
# .env
30+
###> doctrine/doctrine-bundle ###
31+
DATABASE_URL=sqlite:///%kernel.project_dir%/var/data/blog.sqlite
32+
###< doctrine/doctrine-bundle ###
3233
33-
mailer_transport:smtp
34-
mailer_host:127.0.0.1
35-
mailer_user:~
36-
mailer_password:~
34+
###> symfony/swiftmailer-bundle ###
35+
MAILER_URL=smtp://localhost?encryption=ssl&auth_mode=login&username=&password=
36+
###< symfony/swiftmailer-bundle ###
3737
38-
# ...
38+
# ...
3939
40-
These options aren't defined inside the ``app/config/config.yml`` file because
40+
These options aren't defined inside the ``config/services.yaml`` file because
4141
they have nothing to do with the application's behavior. In other words, your
4242
application doesn't care about the location of your database or the credentials
4343
to access to it, as long as the database is correctly configured.
@@ -49,37 +49,32 @@ Canonical Parameters
4949

5050
..best-practice::
5151

52-
Define all your application's parameters in the
53-
``app/config/parameters.yml.dist`` file.
52+
Define all your application's env vars in the ``.env.dist`` file.
5453

55-
Symfony includes a configuration file called ``parameters.yml.dist``, which
56-
stores the canonical list ofconfiguration parameters for the application.
54+
Symfony includes a configuration file called ``.env.dist`` at the project root,
55+
whichstores the canonical list ofenvironment variables for the application.
5756

58-
Whenever a new configuration parameter is defined for the application, you
59-
should also add it to this file and submit the changes to your version control
60-
system. Then, whenever a developer updates the project or deploys it to a server,
61-
Symfony will check if there is any difference between the canonical
62-
``parameters.yml.dist`` file and your local ``parameters.yml`` file. If there
63-
is a difference, Symfony will ask you to provide a value for the new parameter
64-
and it will add it to your local ``parameters.yml`` file.
57+
Whenever a new env var is defined for the application, you should also add it to
58+
this file and submit the changes to your version control system so your
59+
workmates can update their ``.env`` files.
6560

6661
Application-Related Configuration
6762
---------------------------------
6863

6964
..best-practice::
7065

7166
Define the application behavior related configuration options in the
72-
``app/config/config.yml`` file.
67+
``config/services.yaml`` file.
7368

74-
The ``config.yml`` file contains the options used by the application to modify
75-
its behavior, such as the sender of email notifications, or the enabled
76-
`feature toggles`_. Defining these values in ``parameters.yml`` file would
77-
add an extralayer of configuration that's not needed because you don't need
78-
or want theseconfiguration values to change on each server.
69+
The ``services.yaml`` file contains the options used by the application to
70+
modifyits behavior, such as the sender of email notifications, or the enabled
71+
`feature toggles`_. Defining these values in ``.env`` file would add an extra
72+
layer of configuration that's not needed because you don't need or want these
73+
configuration values to change on each server.
7974

80-
The configuration options defined in the ``config.yml``file usuallyvary from
81-
one:doc:`environment</configuration/environments>` to another. That's
82-
why Symfony already includes ``app/config/config_dev.yml`` and ``app/config/config_prod.yml``
75+
The configuration options defined in the ``services.yaml``mayvary from one
76+
:doc:`environment</configuration/environments>` to another. That's why Symfony
77+
supports defining ``config/services_dev.yaml`` and ``config/services_prod.yaml``
8378
files so that you can override specific values for each environment.
8479

8580
Constants vs Configuration Options
@@ -99,7 +94,7 @@ to control the number of posts to display on the blog homepage:
9994

10095
..code-block::yaml
10196
102-
#app/config/config.yml
97+
# config/services.yaml
10398
parameters:
10499
homepage.num_items:10
105100
@@ -167,7 +162,7 @@ just one or two words to describe the purpose of the parameter:
167162

168163
..code-block::yaml
169164
170-
#app/config/config.yml
165+
# config/services.yaml
171166
parameters:
172167
# don't do this: 'dir' is too generic and it doesn't convey any meaning
173168
app.dir:'...'
@@ -178,38 +173,6 @@ just one or two words to describe the purpose of the parameter:
178173
app.dir.contents:'...'
179174
app.contents-dir:'...'
180175
181-
Semantic Configuration: Don't Do It
182-
-----------------------------------
183-
184-
..best-practice::
185-
186-
Don't define a semantic dependency injection configuration for your bundles.
187-
188-
As explained in:doc:`/bundles/extension` article, Symfony bundles
189-
have two choices on how to handle configuration: normal service configuration
190-
through the ``services.yml`` file and semantic configuration through a special
191-
``*Extension`` class.
192-
193-
Although semantic configuration is much more powerful and provides nice features
194-
such as configuration validation, the amount of work needed to define that
195-
configuration isn't worth it for bundles that aren't meant to be shared as
196-
third-party bundles.
197-
198-
Moving Sensitive Options Outside of Symfony Entirely
199-
----------------------------------------------------
200-
201-
When dealing with sensitive options, like database credentials, we also recommend
202-
that you store them outside the Symfony project and make them available
203-
through environment variables:
204-
205-
..code-block::yaml
206-
207-
# app/config/config.yml
208-
doctrine:
209-
dbal:
210-
# ...
211-
password:"%env(DB_PASSWORD)%"
212-
213176
----
214177

215178
Next::doc:`/best_practices/business-logic`

‎best_practices/creating-the-project.rst‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ Installing Symfony
88

99
Use Composer and Symfony Flex to create and manage Symfony applications.
1010

11-
`Composer`_ is the package manager used by modern PHPapplication to manage
11+
`Composer`_ is the package manager used by modern PHPapplications to manage
1212
their dependencies. `Symfony Flex`_ is a Composer plugin designed to automate
1313
some of the most common tasks performed in Symfony applications. Using Flex is
1414
optional but recommended because it improves your productivity significantly.

‎bundles/override.rst‎

Lines changed: 14 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -46,22 +46,24 @@ Services & Configuration
4646
If you want to modify service definitions of another bundle, you can use a compiler
4747
pass to change the class of the service or to modify method calls. In the following
4848
example, the implementing class for the ``original-service-id`` is changed to
49-
``Acme\DemoBundle\YourService``::
49+
``App\YourService``:
5050

51-
// src/Acme/DemoBundle/DependencyInjection/Compiler/OverrideServiceCompilerPass.php
52-
namespace Acme\DemoBundle\DependencyInjection\Compiler;
51+
..code-block::diff
5352
54-
use Acme\DemoBundle\YourService;
55-
use Symfony\Component\DependencyInjection\Compiler\CompilerPassInterface;
56-
use Symfony\Component\DependencyInjection\ContainerBuilder;
53+
// src/Kernel.php
54+
namespace App;
5755
58-
class OverrideServiceCompilerPass implements CompilerPassInterface
56+
// ...
57+
+ use App\Service\YourService;
58+
+ use Symfony\Component\DependencyInjection\ContainerBuilder;
59+
60+
class Kernel extends BaseKernel
5961
{
60-
public function process(ContainerBuilder $container)
61-
{
62-
$definition = $container->getDefinition('original-service-id');
63-
$definition->setClass(YourService::class);
64-
}
62+
+ public function process(ContainerBuilder $container)
63+
+ {
64+
+$definition = $container->findDefinition('original-service-id');
65+
+ $definition->setClass(YourService::class);
66+
+ }
6567
}
6668
6769
For more information on compiler passes, see:doc:`/service_container/compiler_passes`.

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp