tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-10-22 14:05:37 +02:00
Code Issues Projects Releases Wiki Activity

Merge pull request #8652 from edlinklater/patch-2

Browse Source 
FIX incorrect composer module type
This commit is contained in:
Robbie Averill 2018-11-30 19:55:08 +01:00 committed by GitHub
commit f1170255cb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/en/02_Developer_Guides/05_Extending/How_Tos/01_Publish_a_Module.md
View File

@ -57,7 +57,7 @@ up by [addons.silverstripe.org](http://addons.silverstripe.org/) website due to
Note that SilverStripe modules have the following distinct characteristics: Note that SilverStripe modules have the following distinct characteristics:
- SilverStripe can hook in to the composer installation process by declaring `type: silverstripe/vendormodule`. - SilverStripe can hook in to the composer installation process by declaring `type: silverstripe-vendormodule`.
- Any folder which should be exposed to the public webroot must be declared in the `extra.expose` config. - Any folder which should be exposed to the public webroot must be declared in the `extra.expose` config.
These paths will be automatically rewritten to public urls which don't directly serve files from the `vendor` These paths will be automatically rewritten to public urls which don't directly serve files from the `vendor`
folder. For instance, `vendor/my-vendor/my-module/client` will be rewritten to folder. For instance, `vendor/my-vendor/my-module/client` will be rewritten to