Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for Cockpit CMS #284

Merged
merged 2 commits into from
Jul 28, 2016
Merged

Add support for Cockpit CMS #284

merged 2 commits into from
Jul 28, 2016

Conversation

piotr-cz
Copy link
Contributor

@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 like public/cockpit, specify it's path in root composer.json file like so

"extra": {
    "installer-paths": {
        "public/cockpit/modules/addons/{$name}": ["type:cockpit-module"]
    }
}

Same 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants