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

Install CKEditor through Composer #3

Open
raeldc opened this issue Nov 25, 2015 · 2 comments
Open

Install CKEditor through Composer #3

raeldc opened this issue Nov 25, 2015 · 2 comments
Labels
Milestone

Comments

@raeldc
Copy link
Contributor

raeldc commented Nov 25, 2015

No need to save the whole editor in the repo. We can install it through Composer.

http://docs.ckeditor.com/#!/guide/dev_package_managers

@johanjanssens
Copy link
Member

@raeldc True, the problem with this approach is that it will install it in the vendor folder. Vendor folder lives below HTTP root. As a result you will need additional rewrite rules to be able to get to the resources. This is not ideal.

Other projects solved this by either symlinking or copying the resources to the proper location. We do not have an asset management solution for this yet that can handle this.

@johanjanssens johanjanssens added this to the Backlog milestone Nov 25, 2015
@johanjanssens
Copy link
Member

@ercanozkaya When working on our composer installers can we also add support for custom folders so that we do not need to install CKEditor in the repo?

See also: https://getcomposer.org/doc/faqs/how-do-i-install-a-package-to-a-custom-path-for-my-framework.md

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

No branches or pull requests

2 participants