Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@this PR adds support for custom Cockpit CMS modules that are installed in
[cockpit-path]/modules/addons/
folder. There is no support for core modules, which are distributed with the platform at the moment.Module's composer.json file should contain the type: "cockpit-module" and name: "vendorName/cockpit-moduleName".
If you've installed Cockpit into other directory than
cockpit
or directory under root likepublic/cockpit
, specify it's path in root composer.json file like soSame installer can be used for cockpit-next and cockpit installation inside cocopi-kickstart.
@aheinze
I'm not sure how if the added $prefix parameter in the Lime\App::loadModules method you introduced in agentejo/cockpit@73552f3 can add possibility to change module name creation