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

Commit797aab7

Browse files
committed
Fixed minor issues
1 parenta75cc15 commit797aab7

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

‎cookbook/configuration/environments.rst‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,13 +5,13 @@ How to Master and Create new Environments
55
=========================================
66

77
Every application is the combination of code and a set of configuration that
8-
dictates how that code should function. The configuration may define the
9-
databasebeing used, if something should be cached or how verbose
10-
logging should be. In Symfony, the idea of "environments" is the idea that
11-
thesame codebase can be run using multiple different configurations. For
12-
example, the ``dev`` environment should use configuration that makes development
13-
easy and friendly, while the ``prod`` environment should use a set of configuration
14-
optimized for speed.
8+
dictates how that code should function. The configuration may define the database
9+
being used, if something should be cached or how verbose logging should be.
10+
11+
In Symfony,theidea of "environments" is the idea that the same codebase can be
12+
run using multiple different configurations. Forexample, the ``dev`` environment
13+
should use configuration that makes development easy and friendly, while the
14+
``prod`` environment should use a set of configurationoptimized for speed.
1515

1616
..index::
1717
single: Environments; Configuration files

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp