...
Legacy applications can be referenced both by new Innomatic Platform based applications and legacy applications that have been updated with a composer.json file.
Installing legacy applications with Composer dependencies at runtime
While you would normally edit the root project composer.json file to define your dependencies, you can also deploy new applications at run time as in the old Innomatic 6.x way so you don't have to change the root composer.json file. This also applies to legacy applications updated with a composer.json file. You can think of them as plugins that are installed by an administrator after the platform has been installed.
Since Composer doesn't still natively support recursive dependencies, we have added this sort of support in Innomatic using the Wikimedia Composer merge plugin so that new applications with a composer.json file can be added at run time without changing the root composer.json file.
To avoid timeouts we recommend installing applications with Composer dependencies using the applications.php CLI script in place of the applications web control panel.
You can check inside the code if a valid Composer autoloader is available through the \Innomatic\Core\RootContainer->hasComposer() method. In that case, any package installed in the vendor directory using Composer is available to Innomatic Legacy through the Composer autoloader.
Running legacy scripts
Legacy scripts can be executed from the Symfony CLI, by using the innomatic:legacy:script command, specifying the script name without the path as argument.
...