Skip to content
Snippets Groups Projects

#3368811: Help text for config clone has been added

Open #3368811: Help text for config clone has been added
issue/drupal-3368811:3368811-help-text-for-config-clone into 11.x
4 unresolved threads
Open Martin Mayer requested to merge issue/drupal-3368811:3368811-help-text-for-config-clone into 11.x
4 unresolved threads

Closes #3368811

Merge request reports

Members who can merge are allowed to add commits.

Merge request pipeline #459165 failed

Stage: 🏗️ Build
Stage: 🪄 Lint
Stage: 🗜️ Test
Pipeline: drupal-3368811

#459171

    Merge request pipeline failed for 8e18f24b

    Approval is optional
    Code Quality is loading
    Test summary results are being parsed
    Full report
    Ready to merge by members who can write to the target branch.

    Merge details

    • The source branch is 2229 commits behind the target branch.
    • 1 commit and 1 merge commit will be added to .
    • Source branch will not be deleted.

    Activity

    Filter activity
    • Approvals
    • Assignees & reviewers
    • Comments (from bots)
    • Comments (from users)
    • Commits & branches
    • Edits
    • Labels
    • Lock status
    • Mentions
    • Merge request status
    • Tracking
    core/modules/help/help_topics/core.config_overview.html.twig
    38 38 <dt>{% trans %}Configuration sync directory{% endtrans %}</dt>
    39 39 <dd>{% trans %}The configuration sync directory location is set in the site's <em>settings.php</em> file. When configuration is exported, the active configuration is exported and described in YAML files which are stored in the configuration sync directory. After the first export, the system compares the site's active configuration with the configuration data in the sync directory and will only export active configuration items that are different than their counterparts in the sync directory.{% endtrans %}</dd>
    40 40 </dl>
    41 <h2>{% trans %}Installing a new site from an existing config{% endtrans %}</h2>
    42 <p>{% trans %}You can create a new site from an existing site, if you want an identical configuration.{% endtrans %}</p>
    43 <dl>
    44 <dt>{% trans %}Copy config files{% endtrans %}</dt>
    45 <dd>{% trans %}Copy the files from the existing config directory into the new configuration directory{% endtrans %}</dd>
  • Joachim Noreiko
    Joachim Noreiko @joachim started a thread on an old version of the diff
    • core/modules/help/help_topics/core.config_overview.html.twig
    38 38 <dt>{% trans %}Configuration sync directory{% endtrans %}</dt>
    39 39 <dd>{% trans %}The configuration sync directory location is set in the site's <em>settings.php</em> file. When configuration is exported, the active configuration is exported and described in YAML files which are stored in the configuration sync directory. After the first export, the system compares the site's active configuration with the configuration data in the sync directory and will only export active configuration items that are different than their counterparts in the sync directory.{% endtrans %}</dd>
    40 40 </dl>
    41 <h2>{% trans %}Installing a new site from an existing config{% endtrans %}</h2>
    42 <p>{% trans %}You can create a new site from an existing site, if you want an identical configuration.{% endtrans %}</p>
    43 <dl>
    44 <dt>{% trans %}Copy config files{% endtrans %}</dt>
    45 <dd>{% trans %}Copy the files from the existing config directory into the new configuration directory{% endtrans %}</dd>
    46 <dt>{% trans %}Import with drush{% endtrans %}</dt>
    47 <dd>{% trans %}drush site:install --existing-config will install a new site, using the configuration from an existing config. This will overwrite anything in the database!{% endtrans %}</dd>
  • Khalim Harris added 1 commit

    added 1 commit

    Compare with previous version

  • Stephen Mustgrave
    Stephen Mustgrave @smustgrave started a thread on the diff
    • core/modules/help/help_topics/core.config_overview.html.twig
    38 38 <dt>{% trans %}Configuration sync directory{% endtrans %}</dt>
    39 39 <dd>{% trans %}The configuration sync directory location is set in the site's <em>settings.php</em> file. When configuration is exported, the active configuration is exported and described in YAML files which are stored in the configuration sync directory. After the first export, the system compares the site's active configuration with the configuration data in the sync directory and will only export active configuration items that are different than their counterparts in the sync directory.{% endtrans %}</dd>
    40 40 </dl>
    41 <h2>{% trans %}Installing a new site from an existing config{% endtrans %}</h2>
    42 <p>{% trans %}You can create a new site from an existing site, if you want an identical configuration.{% endtrans %}</p>
  • Stephen Mustgrave
    Stephen Mustgrave @smustgrave started a thread on the diff
    • core/modules/help/help_topics/core.config_overview.html.twig
    38 38 <dt>{% trans %}Configuration sync directory{% endtrans %}</dt>
    39 39 <dd>{% trans %}The configuration sync directory location is set in the site's <em>settings.php</em> file. When configuration is exported, the active configuration is exported and described in YAML files which are stored in the configuration sync directory. After the first export, the system compares the site's active configuration with the configuration data in the sync directory and will only export active configuration items that are different than their counterparts in the sync directory.{% endtrans %}</dd>
    40 40 </dl>
    41 <h2>{% trans %}Installing a new site from an existing config{% endtrans %}</h2>
    42 <p>{% trans %}You can create a new site from an existing site, if you want an identical configuration.{% endtrans %}</p>
    43 <dl>
    44 <dt>{% trans %}Copy config files{% endtrans %}</dt>
  • Stephen Mustgrave left review comments

    left review comments

    • Please register or sign in to reply