./script/solar link-vendor
VendorName
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
the 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
make-vendor command.)
To link a vendor source into a Solar system, issue the following command:
$./script/solar link-vendor
Making links for vendor 'VendorName
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 forVendorName
_Controller_Bread ... done. Making public symlink forVendorName
_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 theinclude/
directory, including test cases, test mocks, and test fixtures. It also creates a link so thatscript/
commands are available.vendor-name
-
Next, the command links the
Public/
direcory in all PHP classes for the vendor to thedocroot/public
directory, so that public assets for a class are available via the web.