You are here

README.txt in Drupal 8

Same filename in this branch
  1. 8 README.txt
  2. 8 themes/README.txt
  3. 8 sites/README.txt
  4. 8 profiles/README.txt
  5. 8 modules/README.txt
  6. 8 composer/Template/README.txt
  7. 8 composer/Metapackage/README.txt
  8. 8 core/lib/README.txt
  9. 8 composer/Plugin/VendorHardening/README.txt
  10. 8 core/themes/stark/README.txt
  11. 8 core/themes/classy/README.txt
  12. 8 core/themes/seven/README.txt
  13. 8 core/themes/stable/README.txt
  14. 8 core/themes/bartik/README.txt
  15. 8 core/assets/scaffold/README.txt
  16. 8 core/lib/Drupal/Core/README.txt
  17. 8 core/lib/Drupal/Component/README.txt
  18. 8 core/tests/fixtures/files/README.txt
  19. 8 core/lib/Drupal/Component/Datetime/README.txt
  20. 8 core/lib/Drupal/Component/DependencyInjection/README.txt
  21. 8 core/lib/Drupal/Component/Transliteration/README.txt
  22. 8 core/lib/Drupal/Component/FileSystem/README.txt
  23. 8 core/lib/Drupal/Component/Utility/README.txt
  24. 8 core/lib/Drupal/Component/Assertion/README.txt
  25. 8 core/lib/Drupal/Component/HttpFoundation/README.txt
  26. 8 core/lib/Drupal/Component/Annotation/README.txt
  27. 8 core/lib/Drupal/Component/Diff/README.txt
  28. 8 core/lib/Drupal/Component/FileSecurity/README.txt
  29. 8 core/lib/Drupal/Component/ProxyBuilder/README.txt
  30. 8 core/lib/Drupal/Component/Discovery/README.txt
  31. 8 core/lib/Drupal/Component/Serialization/README.txt
  32. 8 core/lib/Drupal/Component/EventDispatcher/README.txt
  33. 8 core/lib/Drupal/Component/FileCache/README.txt
  34. 8 core/lib/Drupal/Component/ClassFinder/README.txt
  35. 8 core/lib/Drupal/Component/Plugin/README.txt
  36. 8 core/lib/Drupal/Component/Gettext/README.txt
  37. 8 core/lib/Drupal/Component/PhpStorage/README.txt
  38. 8 core/lib/Drupal/Component/Graph/README.txt
  39. 8 core/lib/Drupal/Component/Render/README.txt
  40. 8 core/lib/Drupal/Component/Bridge/README.txt
  41. 8 core/lib/Drupal/Component/Uuid/README.txt
  42. 8 core/lib/Drupal/Component/Version/README.txt
  43. 8 core/themes/claro/css/classy/README.txt
  44. 8 core/themes/claro/templates/classy/README.txt
  45. 8 core/themes/claro/images/classy/README.txt
  46. 8 core/themes/claro/js/classy/README.txt
  47. 8 core/themes/seven/css/classy/README.txt
  48. 8 core/themes/seven/templates/classy/README.txt
  49. 8 core/themes/seven/images/classy/README.txt
  50. 8 core/themes/seven/js/classy/README.txt
  51. 8 core/themes/bartik/css/classy/README.txt
  52. 8 core/themes/bartik/templates/classy/README.txt
  53. 8 core/themes/bartik/images/classy/README.txt
  54. 8 core/themes/bartik/js/classy/README.txt
  55. 8 core/profiles/demo_umami/themes/umami/README.txt
  56. 8 core/profiles/demo_umami/themes/umami/css/classy/README.txt
  57. 8 core/profiles/demo_umami/themes/umami/templates/classy/README.txt
  58. 8 core/profiles/demo_umami/themes/umami/images/classy/README.txt
  59. 8 core/profiles/demo_umami/themes/umami/js/classy/README.txt
  60. 8 core/modules/system/tests/modules/plugin_test/src/Plugin/plugin_test/fruit/README.txt
Same filename and directory in other branches
  1. 9 composer/Plugin/VendorHardening/README.txt
The Drupal Vendor Hardening Composer Plugin
===========================================

Thanks for using this Drupal component.

You can participate in its development on Drupal.org, through our issue system:
https://www.drupal.org/project/issues/drupal

You can get the full Drupal repo here:
https://www.drupal.org/project/drupal/git-instructions

You can browse the full Drupal repo here:
http://cgit.drupalcode.org/drupal

What does it do?
----------------

This Composer plugin does two things:

1) It removes extraneous directories from the project's vendor directory.
They're typically directories which might contain executable files, such as test
directories.

This sort of processing is required for projects that have a vendor directory
inside the HTTP server docroot. This is a common layout for Drupal.

By default, the plugin knows how to clean up packages for Drupal core, so you
can require drupal/core-vendor-hardening in your project and the rest will
happen automatically.

The plugin can also be configured to clean up additional packages using the
project's composer.json extra field.

2) The plugin also adds .htaccess and web.config files to the root of the
project's vendor directory. These files will do due diligence to keep the web
server from serving files from within the vendor directory.

How do I set it up?
-------------------

Require this Composer plugin into your project:

    composer require drupal/core-vendor-hardening

When you install or update, this plugin will look through each package and
remove directories it knows about.

You can see the list of default package cleanups for this plugin in Config.php.
If you discover that this list needs updating, please file an issue about it:
https://www.drupal.org/project/issues/drupal

In addition to the default list of packages, you can configure the plugin using
the root package's composer.json extra field, like this:

    "extra": {
      "drupal-core-vendor-hardening": {
        "vendor/package": ["test", "documentation"]
      }
    }

The above code will tell the plugin to remove the test/ and documentation/
directories from the 'vendor/package' package when it is installed or updated.

File

composer/Plugin/VendorHardening/README.txt
View source
  1. The Drupal Vendor Hardening Composer Plugin
  2. ===========================================
  3. Thanks for using this Drupal component.
  4. You can participate in its development on Drupal.org, through our issue system:
  5. https://www.drupal.org/project/issues/drupal
  6. You can get the full Drupal repo here:
  7. https://www.drupal.org/project/drupal/git-instructions
  8. You can browse the full Drupal repo here:
  9. http://cgit.drupalcode.org/drupal
  10. What does it do?
  11. ----------------
  12. This Composer plugin does two things:
  13. 1) It removes extraneous directories from the project's vendor directory.
  14. They're typically directories which might contain executable files, such as test
  15. directories.
  16. This sort of processing is required for projects that have a vendor directory
  17. inside the HTTP server docroot. This is a common layout for Drupal.
  18. By default, the plugin knows how to clean up packages for Drupal core, so you
  19. can require drupal/core-vendor-hardening in your project and the rest will
  20. happen automatically.
  21. The plugin can also be configured to clean up additional packages using the
  22. project's composer.json extra field.
  23. 2) The plugin also adds .htaccess and web.config files to the root of the
  24. project's vendor directory. These files will do due diligence to keep the web
  25. server from serving files from within the vendor directory.
  26. How do I set it up?
  27. -------------------
  28. Require this Composer plugin into your project:
  29. composer require drupal/core-vendor-hardening
  30. When you install or update, this plugin will look through each package and
  31. remove directories it knows about.
  32. You can see the list of default package cleanups for this plugin in Config.php.
  33. If you discover that this list needs updating, please file an issue about it:
  34. https://www.drupal.org/project/issues/drupal
  35. In addition to the default list of packages, you can configure the plugin using
  36. the root package's composer.json extra field, like this:
  37. "extra": {
  38. "drupal-core-vendor-hardening": {
  39. "vendor/package": ["test", "documentation"]
  40. }
  41. }
  42. The above code will tell the plugin to remove the test/ and documentation/
  43. directories from the 'vendor/package' package when it is installed or updated.