The link-vendor command creates a series of
standard symbolic links in a Solar system for a given vendor. If you
copy the vendor files from another project into your
source directory, they won't be accessible via
include directory, nor will the public assets
be available via
docroot/public. This command
creates the symbolic links for you so they will be accessible. (Vendor
linking happens automatically as part of the
To link a vendor source into a Solar system, issue the following command:
./script/solar link-vendorMaking links for vendor '
VendorName' ... Making link 'include/
VendorName' ... done. Making link 'include/Test/
VendorName' ... done. Making link 'include/Mock/
VendorName' ... done. Making link 'include/Fixture/
VendorName' ... done. Making link 'script/
vendor-name' ... done. ... done. Making public symlinks for '
VendorName' ... Making public directory docroot/public/
VendorName/Controller ... done. Making public symlink for
VendorName_Controller_Bread ... done. Making public symlink for
VendorName_Controller_Page ... done. ... done. Remember to add '
VendorName_App' to the ['Solar_Controller_Front']['classes'] element in your config file so that it finds your apps. Remember to add '
VendorName_Model' to the ['Solar_Sql_Model_Catalog']['classes'] element in your config file so that it finds your models. $
What is going on here?
The command creates symbolic links from the
source/directory to the
include/directory, including test cases, test mocks, and test fixtures. It also creates a link so that
script/commands are available.
Next, the command links the
Public/direcory in all PHP classes for the vendor to the
docroot/publicdirectory, so that public assets for a class are available via the web.