Implements packages management and bundles load without necessity to update application files.
Add Resources/config/oro/bundles.yml file to every bundle you want to be autoregistered:
bundles:
- VendorName\Bundle\VendorBundle\VendorAnyBundle
- My\Bundle\MyBundle\MyCustomBundle
# - ...
That's it! Your bundle (and "VendorAnyBundle") will be automatically registered in AppKernel.php.
Add Resources/config/oro/routing.yml file to every bundle for which you want to autoload its routes.
Add following rule to application's routing.yml
:
oro_auto_routing:
resource: .
type: oro_auto
All routes from your bundles will be imported automatically.
There are console commands 6 console commands: for installing, updating packages, viewing lists of installed in the system projects, packages available for installation and available updates for installed packages
Command syntax is: oro:package:install [-f|--force] package [version]
package
- name of the package you want to be installed (vendor/package
)version
- version of the package. Optional parameter. If omitted latest available version will be installed base onminimum-stability
setting of the rootcomposer.json
file. Version can be specified in any format acceptable by composer (1.0.2
,>v0.1, <=0.3
)--force
- if command run with this option all package dependencies will be installed/updated along with the package. If omitted - command will ask about required packages(if any), process may be either continued or aborted then.
Command syntax is: oro:package:update package
package
- name of the package you want to be updated (vendor/package
). Package will be updated to the latest available in repository and acceptable by application version (defined in rootcomposer.json
).
Along with installing/updating install/update scripts are being executed.
install.php
- install script of a package
update_<version>.php
- update script of a package. <version>
- package version being updated to. Package must contain update scripts of all previous package versions so that migrations could be applied one by one. E.g if package is being update from v1
to v3
, then update_v2.php
and update_v3.php
will be executed.
Note: v
is not required symbol for update script name (update_v1.php
). v
is part of version name. <version>
is version as it is in package composer.json
.
Examples:
-update_v1.5.php
means that package has version v1.5
(literally).
-update_0.1.1.php
means that there is 0.1.1
version of a package.
Command syntax is oro:package:installed
.
Displays currently installed packages (excluding packages from https://packagist.org) along with versions
Command syntax is oro:package:available
.
Displays packages available in repositories (excluding packages from https://packagist.org)
Command syntax is oro:package:updates
.
Displays available updates for installed packages along with currently installed version and the latest available version.
If package is not stable (package version is dev-master
) then hash of latest commit is displayed.