View more context



Yes. SilverStripe is pretty portable once it's up and running

👍 (1)

got a question about composer.json -> extra -> installer-name, recently we developed a vendor module which has a really long name, e.g. mycompany/silverstripe-several-words-very-long and for installation, I want the directory name to be a little shorter than silverstripe-several-words-very-long. I thought the installer-name under extra in composer.json is the place I could customize the directory name, but I am wrong, as I give it a short name there, but it doesn't affect. Anyone knows what do I need to do, instead of using the installer-name.


The vendor-module should be very concise, and not contain silverstripe-, so it would by mycompany/concise-name, and that would make it install in to vendor/mycompany/concise-name


Your repo can still be silverstripe-several-words-very-long though


@Firesphere thanks. I will try to shorten the module name then.


For those wondering: installer-name is something specific to "type": "silverstripe-module", and is not a general composer command (afaik). This is also what installed the dependencies into the project root, instead of the vendor directory. This no longer applies with SS4 using "type": "silverstripe-vendormodule" - this puts things in normal PSR-4 style (in vendor - i.e. does nothing special with the install) and exists more for vendor-expose support.


But, a reminder that the packagist vendor/module-name format doesn't have to mirror the repository address (e.g. on github). Furthermore there is the replace composer config directive which one can use to rename their modules (c.f. friendsofsilverstripe becoming bringyourownideas:

Show 1 attachment(s)

Helps with the day by day work to run a SilverStripe application or website. - bringyourownideas/silverstripe-maintenance

Hide attachment content