[TASK] Improve description of config preset in install tool 32/23832/4
authorSteffen Müller <typo3@t3node.com>
Sat, 14 Sep 2013 14:39:23 +0000 (16:39 +0200)
committerJigal van Hemert <jigal.van.hemert@typo3.org>
Sat, 14 Sep 2013 15:09:33 +0000 (17:09 +0200)
Resolves: #52007
Releases: 6.2
Change-Id: I4c8bb6930040a9f3a5c5bc92c9638a98a2668daf
Reviewed-on: https://review.typo3.org/23832
Reviewed-by: Wouter Wolters
Tested-by: Wouter Wolters
Reviewed-by: Philipp Gampe
Tested-by: Philipp Gampe
Reviewed-by: Jigal van Hemert
Tested-by: Jigal van Hemert
typo3/sysext/install/Resources/Private/Partials/Action/Tool/Configuration/Context.html

index 2440873..4ee1b64 100644 (file)
@@ -5,16 +5,20 @@
 
        <div class="toggleData" style="display:none">
                <p>
-                       A set of configuration options should be different if the current
-                       environment is a development or a production system. The goal is
-                       to configure a production instance with maximum performance and no
-                       debug output that is possibly shown to users, while development
-                       instances should enable error output.
+                       TYPO3 can be run in a specific application context by using one of the
+                       built-in contexts "Production" (default), "Development" or "Testing".
+                       This can be used to provide specific configuration sets for each context.
+                       The context can be defined with the environment variable "TYPO3_CONTEXT"
+                       which is usually set through your webserver configuration (e.g. in htaccess).
                </p>
                <p>
-                       The environment can be defined with the environment variable
-                       "TYPO3_CONTEXT" set to "Production" or "Development". If no context
-                       environment variable is set, "Production" is assumed.
+                       However, if you don't set a context environment variable, you can still
+                       use the install tool to select a configuration preset for "Production"
+                       or "Development" context. The goal is to configure a production instance
+                       with maximum performance and no debug output that is possibly shown to users,
+                       while development instances should enable error output. The configuration
+                       preset for "Production" is set by default.
+                       As a third alternative, you can enter a custom configuration.
                </p>
 
                <f:for each="{feature.presetsOrderedByPriority}" as="preset">